Replies: 1 comment
|
Hi @T3sT3ro, thanks for the suggestion. At some point, FM used this library for various components, but webcomponents in React sometimes caused issues. Like event binding and such, that is why I started https://github.com/estruyf/vscrui The idea is similar like the library you mentioned, but the components are React based which makes it easier to configure and use. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi, would you be open to the idea of incorporating the https://vscode-elements.github.io and slowly migrating the components to that library for the sake of uniformity with the rest of the vscode GUI?
The work regarding that could potentially slim down the codebase significantly by migrating from custom components and styles to the ones that feel native to the editor out of the box. Other advantages include potentially improved accessibility, better UX and eventually lead to more time for working on features of the extension instead of the components.
What do you think about that, would you be open the the PRs of that nature? I think it could be done in small bits, migrating stuff component by component, so there would be no fear of doing massive refactors. If you were interested in that idea, I could try to work on a POC of that!
All reactions