Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Parameters are not considered

See original GitHub issue

I’m having a problem passing parameters. Despite having followed the guide, the parameters of the translation are not taken into consideration. This is the svelte code $t( 'PRIVACY_POLICY', { values: { link: 'abc' } } ) And this is the translation "PRIVACY_POLICY": "Privacy <a href=\"{ link }\">policy</a>"

Issue Analytics

State:
Created 2 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

cibernoxcommented, Nov 18, 2021

If that’s the case you’ve proven that I should add some console warning if the specified locales folder doesn’t exist instead of silently doing nothing.

0reactions

cibernoxcommented, Nov 19, 2021

I checked and under normal circumstances the app already complaints if there aren’t any translation in the specified folder as soon as you try to import them.

Your scenario was rather unusual because the fact that you had already defined an alias for src/locales (I’ve just learned that user-defined aliases take precedence, although makes sense) means you never actually imported the locales so the library never kicked in and it didn’t have a chance to warn you.

I’m going to close this issue and continue on #10

Top Results From Across the Web

Why are optional constructor parameters are not considered ...

I register this implementation as follows: Container.RegisterType(typeof(ITranslator), typeof(SignalTranslator));. Since all constructor ...

Consider parameters vs Solve-for parameters in regression

I'm trying to find the correct terminology to use to separate between "consider" parameters (included in the regression model, but held fixed ...

Parameter - Wikipedia

In frequentist estimation parameters are considered "fixed but unknown", whereas in Bayesian estimation they are treated as random variables, and their ...

Parameters not used by Planning Optimization | Dynamics 365

This article lists the parameters that Planning Optimization doesn't currently consider during its operation.

STAAD Connect - Unbraced Length Parameters Not ...

My member element in STAAD is only 0.61-m however I want to analyze it at 2.4-m because that's the total length of the...