-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sync between source and manifest #106
Comments
src > manifest is covered by @custom-elements-manifest/analyzer Comparing the latest released manifest and package release semver with current code could be based on ^^ generator and Perhaps this conversation could be moved to @open-wc project as toolchain for web components is not in scope /webcomponents group? |
sashafirsov
changed the title
sync between source and manifect
sync between source and manifest
Apr 17, 2022
I'm having a hard time following this. What's the issue with the schema? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2-way sync or at least validation should be part of toolchain.
Web Component often has sufficient data in sources to generate manifest, hence there is ability to create match validators which are essential for release lifecycle:
pre-release
build levelThe singe source of truth would prevent the mismatch between src and manifest.
The editors actually do not need to use manifest as info could be available in runtime of class implementation. But the listing of components, search and filtering would benefit from manifest format. Having runtime info and manifest in sync would prevent the editor misuse.
The text was updated successfully, but these errors were encountered: