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
thanks for your great work! I encountered a smallish problem where the extractor fails to extract context strings that are not string literals from js/ts files. I like to put all my context strings into a typescript const enum to keep them dry.
Would it be feasible for your parser to resolve identifiers that point to stringifyable const and enum values in context arguments?
The text was updated successfully, but these errors were encountered:
Hi, that's an interesting idea. While it is technically possible, I'm not sure it's in the scope of this project. I'll keep this issue open for the time being though. If other people are looking for this too, I might reconsider.
Hi,
thanks for your great work! I encountered a smallish problem where the extractor fails to extract context strings that are not string literals from js/ts files. I like to put all my context strings into a typescript const enum to keep them dry.
Would it be feasible for your parser to resolve identifiers that point to stringifyable const and enum values in context arguments?
The text was updated successfully, but these errors were encountered: