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
When the no-invalid-variables rule runs, it can only shows that a problem has occurred, but it does not show WHERE the problem exists. However, the https://www.npmjs.com/package/@formatjs/icu-messageformat-parser we use in the project does return the location where the malformed syntax is in the string. It would be really cool to somehow highlight the location of the error where the ICU format went wrong for ever better feedback for the users.
When the
no-invalid-variables
rule runs, it can only shows that a problem has occurred, but it does not show WHERE the problem exists. However, the https://www.npmjs.com/package/@formatjs/icu-messageformat-parser we use in the project does return the location where the malformed syntax is in the string. It would be really cool to somehow highlight the location of the error where the ICU format went wrong for ever better feedback for the users.For example:
will result in the following output:
This means we could use this location data to return a highlighted string as a the error that gets reported to the logger, something that looks like:
These highlighted strings could become the string sent to the
received
property on theProblem
classThe text was updated successfully, but these errors were encountered: