behavior of loadResource() confusing

[lucidNTR]

Setup:
current main branches of inlang and example app, chrome

Description:
The example app loads resources on mouseover with loadResource(...) on the language toggle which results in a network request to the translation file.

the actual toggle of the language leads to another request to the same language file.

Problem:
the name loadResource sounds to me like the reosource is loaded, parsed and allready in memory, so this behaviour is unexpected and not clear if it is a bug or not.

Possible Solutions:
if the behavior is correct and loadResources is supposed to only prime the browser cache with the resource file, i propose changing the api name to something like prefetchResource().

if the behaviour is a not expected, we should fix reusing allready loaded resources when calling switchLanguage(...)

[samuelstroschein]

Nice catch. I assume that you would want the following of the SDK:

1. load messages (not resources, the concept of resources is removed in #1142)
2. reference messages
3. change languages (no re-initialization of messages)

The current API is likely

1. load messages
2. reference messages
3. change language 
4. reload of messages (exposed to developers)

Ideally, a developer (1) loads messages once and then only (2) reference messages as desired. a change in the language (3) is not exposed.

[ivanhofer]

We need to have a changeLanguage functionality or else you would need to reference messages like this i(language, 'home.title') instead of i('home.title')

[samuelstroschein]

I am aware. The confusion of @lucidNTR seems to stem from explicitly reloading resources (messages). The reloading should (likely) happen under the hood

[lucidNTR]

@samuelstroschein tbh i dont have enough experience with inlang yet to have a strong oppinion about the api/sdk, for me as develpper its only important to have clear expectations what actions result in network requests and when / how many.

[ivanhofer]

The problem was that we

1. fetch the resources from the SvelteKit server
2. then invalidate everything when switching language so we also get new page data (which could contain locale specific content)
3. therefore also resources are refetched again

I have published a new version 0.11.3 that caches the API response in memory to not run into this issue. I will update the example soon.

[ivanhofer]

@lucidNTR Thanks for your investigation!