You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on the use case and which framework is used in a product that shall use the casf document view, the requirements for an integration can be different. A migration to web components can be done much better once the use case and application is known.
As the build options have to be changed and a file for the import as to be created, a migration to web components will be a little bit of work more for implementation and maintenance of this product. Again it is better to have that additional effort when it is needed, but not earlier.
The text was updated successfully, but these errors were encountered:
@ThomasJunk we can keep it open as a possible enhancement. Just because it is not done for 1.0 does not mean it is not done sometimes in the future. ;)
To reuse the single CSAF document view of the repository in different javascript frameworks, consider moving to create standard https://developer.mozilla.org/en-US/docs/Web/API/Web_components .
It is possible to do so in Svelte (e.g. https://blog.logrocket.com/build-web-components-svelte/) which is used so far. It would be possible to use (and create) in VueJS3 as well, see https://vuejs.org/guide/extras/web-components.html#using-custom-elements-in-vue
Considerations
The text was updated successfully, but these errors were encountered: