Burton Smith
Burton Smith
Instead of wrapping the components, can you provide an alternative tag name when in dev or Storybook?
This is kind of cool! So you are basically forcing a reload if the component has already been registered. Are you seeing any performance issues because of this?
This has been added to the latest version of the project: https://wc-toolkit.com/integrations/storybook/
That function syncs the attributes with the Storybook controls. If attributes are updated from within the component, it will update the values in the control. Is the `invalid` attribute settable...
The first piece of this has been created: https://www.npmjs.com/package/cem-plugin-custom-jsdoc-tags
Would you expect that all attributes be displayed in the attributes section and all of the corresponding properties be displayed separately in the properties section? That would bloat up the...
Ah, if you set `reflect: true` in the `@property` decorator, doest that give you the experience you're looking for?
> My only suggestion would be: if the order of our TSDoc matter to other tooling we're trying to support here, then we should enforce that at the Linter level...
> A lot of these changes are adding extra release tags when tags already exist. There should be an `@internal` or `@public`, but not both. @radium-v Technically the `@public` tag...
> This is amazing, but I really don't like adding `@internal` to so many properties. Is there a more ergonomic way we (and or the plugin) can identify properties that...