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
I was not able to receive env-var infos about the OS language during implementing #74. This is based on the fact that raycast only set specific env-vars for the node process.
It would be great when raycast set an env-var (or maybe another typescript-API) to receive the OS language of the user. There are multiple variants I can think of
Variant 1
Pass the LANG, LANGUAGE, LC_ALL, LC_MESSAGES (if they exist) from raycast to the raycast node process. This would be easy to do and maybe other node packages will be based on the same fact.
Variant 2
Raycast provide it's own env-var/typescript-api to make it possible to receive the information in an extension. This variant would be my personal favorite, because raycast can make the access to this setting easy for extension devs.
Describe the feature and the current behavior/state.
Typically I receive the OS language with the following line of code.
As I mentioned in my comment here, at the moment we have no plans to support localization in the app in near future. I'm gonna close that issue for now.
I was not able to receive env-var infos about the OS language during implementing #74. This is based on the fact that raycast only set specific env-vars for the node process.
It would be great when raycast set an env-var (or maybe another typescript-API) to receive the OS language of the user. There are multiple variants I can think of
Variant 1
Pass the
LANG
,LANGUAGE
,LC_ALL
,LC_MESSAGES
(if they exist) from raycast to the raycast node process. This would be easy to do and maybe other node packages will be based on the same fact.Variant 2
Raycast provide it's own env-var/typescript-api to make it possible to receive the information in an extension. This variant would be my personal favorite, because raycast can make the access to this setting easy for extension devs.
Describe the feature and the current behavior/state.
Typically I receive the OS language with the following line of code.
This is not possible in raycast right now, so I'm not able to receive the OS language.
Will this change the current api? How?
No.
Who will benefit with this feature?
Everyone which want to build a multi-language extension for raycast.
Any Other info.
No.
The text was updated successfully, but these errors were encountered: