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
Hi, I found a problem that is actually the opposite of a problem fixed in lingui/js-lingui. After a closer look that bug is extraction, I'm seeing an issue with compilation.
I'll look into building a simple test case, it'll take me awhile, but this really seems like a case of pouring milk into a bowl of cornflakes and getting fire as a result.
For extraction the strings are correctly extracted as "Message {0}" but for the compiled program the second translated string is being treated like "Message {1}"
Hi, I found a problem that is actually the opposite of a problem fixed in lingui/js-lingui. After a closer look that bug is extraction, I'm seeing an issue with compilation.
I'll look into building a simple test case, it'll take me awhile, but this really seems like a case of pouring milk into a bowl of cornflakes and getting fire as a result.
Hi, I think a fix in lingui/js-lingui#2204 likely needs to be applied to hereCode in question
https://github.com/revoltchat/frontend/blob/30abe9801eaac3268a8fe0df04b4987acd7d734d/packages/client/src/interface/channels/text/Composition.tsx#L453-L459
Line 9:
import { useLingui } from "@lingui-solid/solid/macro";
Line 53:
const { t } = useLingui();
Note: I think that means they're using this package/repository
Gets compiled to
For extraction the strings are correctly extracted as "Message {0}" but for the compiled program the second translated string is being treated like "Message {1}"
The text was updated successfully, but these errors were encountered: