Fix prop type validation error if no 'to' specified on portal #45
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
|
Oh dang! Thanks. Seems my test suite is lacking here. I need some functional / integration tests for this... |
|
Sure thing! I'm really excited to see where this project goes, I already see a ton of use-cases for the handful of sites I maintain. |
|
great to hear :) Will merge this tonight hopefully. |
LinusBorg
approved these changes
May 19, 2017
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.
Currently if I leave off the
toprop on aPortaltargeting an element outside the VueApp thePortalTargetthrows a prop type validation error due to aNumberbeing passed in.