[bugfix beta] enable --strict by default to match new app blueprint
#10831
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
mansona
changed the title
--strict by default to match new app blueprint--strict by default to match new app blueprint
mansona
force-pushed
the
strict-default
branch
from
0303ce1 to
056f791
Compare
NullVoxPopuli
approved these changes
Oct 6, 2025
kategengler
approved these changes
Oct 6, 2025
This was referenced Oct 7, 2025
Merged
This was referenced Oct 14, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This matches the behaviour of
@ember/app-blueprintand setting it to--strictby default will keep consistency between blueprints