[FEATURE ember-glimmer-angle-bracket-built-ins] Add missing dependent key#17814
Merged
chancancode merged 1 commit intomasterfrom Mar 29, 2019
Merged
[FEATURE ember-glimmer-angle-bracket-built-ins] Add missing dependent key#17814chancancode merged 1 commit intomasterfrom
chancancode merged 1 commit intomasterfrom
Conversation
Add missing dependent key There are no failing tests for this at the moment, because we only test with all optional features on or off. It turns out that the tracked property feature is masking this failure. As a result, the PR that enables this feature (#17811) without tracked property has some failing tests which should be green again after rebasing on top of this patch.
rwjblue
approved these changes
Mar 28, 2019
5 tasks
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
2 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.
There are no failing tests for this at the moment, because we only test with all optional features on or off. It turns out that the tracked property feature is masking this failure. As a result, the PR that enables this feature (#17811) without tracked property has some failing tests which should be green again after rebasing on top of this patch.