[BUGFIX] Fix contextual components handling invalid component paths #12422
Conversation
This file contains 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
| registry.register( | ||
| 'template:components/-hindi', | ||
| compile(`Namaste`) | ||
| ); |
There was a problem hiding this comment.
Can the above lines of this test be removed? They seem to be un-used.
Contextual components show a message when passed null or unknown component paths.
Serabe
force-pushed
the
feature/null-closure-components
branch
from
200b06a
to
4984afa
Compare
|
#12440 fixed the node-land tests, merging... |
rwjblue
added a commit
that referenced
this pull request
Oct 5, 2015
[BUGFIX] Fix contextual components handling invalid component paths
|
Thank you! |
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.
Contextual components show a message when passed null or unknown component
paths.