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
Is your feature request related to a problem? Please describe
Currently source-loader supports JavaScript, TypeScript and Flow. From what I understand the source-loader powers things like code-snippets as well as documentation provided from JSDoc annotations.
In my project I'm using ReScript which compiles to JavaScript. However, this causes source-loader to look at the compiled JavaScript which loses a lot of documentation and causes incorrect snippets.
Describe the solution you'd like
Ideally I'd like source-loader to support ReScript natively, but I can understand if the current ReScript community is deemed to be too small to have first-party support and maintenance.
I'd be happy to instead be able to swap in a different source loader but from what I understand there's currently no way to change that, so that may need to be built to support the use case.
Describe alternatives you've considered
I've not come up with any other ways to provide Storybook with the required information for correct snippets and component docblocks but I'd be happy if an existing way to do this in userland already exists.
Are you able to assist to bring the feature to reality?
Yes, I'd be happy to help implement this but the way data flows through Storybook from source-code to display in the various plugin is not clear enough for me to know where to start. I'd be looking for pointers on what parts of Storybook to modify.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
Currently source-loader supports JavaScript, TypeScript and Flow. From what I understand the source-loader powers things like code-snippets as well as documentation provided from JSDoc annotations.
In my project I'm using ReScript which compiles to JavaScript. However, this causes source-loader to look at the compiled JavaScript which loses a lot of documentation and causes incorrect snippets.
Describe the solution you'd like
Ideally I'd like source-loader to support ReScript natively, but I can understand if the current ReScript community is deemed to be too small to have first-party support and maintenance.
I'd be happy to instead be able to swap in a different source loader but from what I understand there's currently no way to change that, so that may need to be built to support the use case.
Describe alternatives you've considered
I've not come up with any other ways to provide Storybook with the required information for correct snippets and component docblocks but I'd be happy if an existing way to do this in userland already exists.
Are you able to assist to bring the feature to reality?
Yes, I'd be happy to help implement this but the way data flows through Storybook from source-code to display in the various plugin is not clear enough for me to know where to start. I'd be looking for pointers on what parts of Storybook to modify.
The text was updated successfully, but these errors were encountered: