Bug: Generate projects, even if project don't have any components. Improved UIDL validations for root and component UIDL #500
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.
#487
We use
ComponentUIDL
to carry out all operations needs for generating components. But we use the ComponentUIDL for maintainingroot
inProjectUIDL
. But there are slight changes needed in order to validate.Root Component UIDL
Component UIDL
In
root
thestateDefinitions
are not optional but in component they are optional. Since in root we need them to construct routes. So, ti handle this unique validations no we have two diff validators for components.componentUIDLValidator
androotComponentUIDLValidator
.By default the
@teleporthq/teleport-component-generator
usescomponentUIDLValidator
unless a flag is explicitly passed to userootComponentValidator
.Like this
When this flag is passed, it starts to validate the component using
rootComponentValidator
. This is automatically handled by our project generators while validating a project.projectUIDL