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
While testing a new tooltip for translators about how to correctly translate curly brace patterns, I noticed that our validation wasn't running correctly for a string key with markup and double curly braces in ab/diffusion:
How it's supposed to look:
Some questions:
Is this happening in Rosetta 1.0?
No.
Is this happening for all string keys with both markup and curly braces?
Wow, interestingly, no. This isn't an issue in ab/fourier-making-waves:
Is this happening for string keys with markup and single curly braces?
Seemingly, no.
See ab/acid-base-solutions pattern.0value.1power.
See ab/forces-and-motion-basics pattern.0name.1valueUnitsAcceleration.
The text was updated successfully, but these errors were encountered:
I think I know what the issue is. The makeValidationSchema.js module was written before we added support for shared strings. I bet tAvg and tAvgK are shared strings, and those strings aren't getting validation schemas. Going to try to validate my hypothesis.
liammulh
changed the title
Curly brace validation not working for string keys with markup
Curly brace validation not working for shared string keys
Jan 6, 2023
While testing a new tooltip for translators about how to correctly translate curly brace patterns, I noticed that our validation wasn't running correctly for a string key with markup and double curly braces in ab/diffusion:
How it's supposed to look:
Some questions:
Is this happening in Rosetta 1.0?
Is this happening for all string keys with both markup and curly braces?
Wow, interestingly, no. This isn't an issue in ab/fourier-making-waves:
The text was updated successfully, but these errors were encountered: