Samuel Stroschein
Samuel Stroschein
> Routes is completely UI framework agnostic and can be used by the user/framework's implementation. That makes sense. Users are required to provide their own component.
@jldec 1. i propose to suffix the new interfaces with `V2` and remove the suffix once we release the SDK in a new major version similar to https://github.com/opral/inlang-message-sdk/issues/45#issuecomment-2096282401 2. https://linear.app/opral/issue/MESDK-84/get-rid-of-versioned-interface-packages...
> @jldec (no need for a new versioned-interface package, right) correct.
closing this as we have a new editor component upcoming
Would adding [github/inlang/inlang](https://github.com/inlang/inlang) to this repository help with the translation effort? I could open a PR that adds the config file. Nothing else is required. Contributions open a PR.
@gfwilliams Inlang is supposed to become the "localization" layer one can use to reduce the effort of localization from source code-related things to receiving a UI to edit translations in...
> It makes me think that going forward it might make sense to find a way to encourage apps to use icons/images instead of text What would be the benefit?...
Close in favor of #3057 ?
NodeJS is working after this https://github.com/sqlite/sqlite-wasm/pull/94 PR has been merged, replacing `self` with `globalThis`. I think this PR can be closed.
go for option 1: split by bundle (we have to do this anyways). for prototyping you likely don't need to re-implement @martin-lysk's namespacing algorithm to avoid more than 1000 files...