wip: custom-elements-manifest support #84
Closed
Conversation
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
note: the order of operations in package.json scripts is important since cem/a mutates the customElements field in package.json
|
@web-padawan I think this is feature complete now. Please check knobs for type number. |
|
Closing in favor of #92 |
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.
Closes #63
Closes #61
Manifest loads and components render. The knobs need a little attention to make sure they infer the correct type. Ideally the knobs would be completely separate from the manifest data structure and managed outside the ui
This is also blocked by an issue in custom-elements-manifest analyzer which doesn't add exports for lit customElement decorator definitionsuse this manually editted manifest:nvm i forgot to pass the
--litelementflag to cem/a