Expand native web compatibility and add preflight - #36
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mxrb preflightcommand that audits the renderer actually selected for Mendix 6/7/9/11findDOMNodecompatibilityValidation
bundle exec rubocop: 222 files, 0 offensesmx check: SLA and Sudoku 0 errorsExplicit boundary
Legacy Mendix 6/7/9 builds still use the Dojo renderer, where only Data Grid 1 is compiled. The new preflight reports those unsupported legacy widgets accurately instead of auditing them through the Mendix 11 React path. Mendix 5/8/10 remain fail-closed without audited seeds.
The prior absolute 100% coverage default remains available locally. CI uses separate 98% line and 95% branch floors plus the pinned real-project acceptance run; private Team Server credentials are not required.