fix: fix 'Unknown custom element' without any content (#1426) #1699
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
**Bug**: example, use `<Content />` in a custom page without markdown, will raise `[Vue warn]: Unknown custom element`, like #1173 #1426 **Reason**: because it not inject any content in `@internal/page-components` while not find markdown file, `Vue.component` of `pageKey` must be `undefined`, then `h(pageKey)` raise this error **Fix**: judge as `if (Vue.component(pageKey))`, unnecessary to render if no component existed
|
@ulivz |
|
This is also happening for me. Would love to see this get in soon |
|
ulivz
approved these changes
Jul 20, 2019
|
Hey @zthxxx, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚 |
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
Bug: example, use
<Content />in a custom page without markdown, will raise[Vue warn]: Unknown custom element, like #1173 #1426Reason: because it not inject any content in
@internal/page-componentswhile not find markdown file,Vue.componentofpageKeymust beundefined, thenh(pageKey)raise this errorFix: judge as
if (Vue.component(pageKey)), unnecessary to render if no component existedWhat kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx], where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: