I believe the update recently to AspNetCore.Localizer.Json broke some of the code in our web app, not sure if others have experienced any issues, but it was something our build pipelines picked up as the team was committing changes .
Still doing some investigating, but it affected us here where we're localizing and interpolating a string.
and here, where we were localizing an empty string.
Again still investigating this as we had multiple changes in the pipe, but the timing of the failed tests and the change in localizer between PR's seems to be pointing to this.
Posting this for viability,
I believe the update recently to AspNetCore.Localizer.Json broke some of the code in our web app, not sure if others have experienced any issues, but it was something our build pipelines picked up as the team was committing changes .
Still doing some investigating, but it affected us here where we're localizing and interpolating a string.
and here, where we were localizing an empty string.
Again still investigating this as we had multiple changes in the pipe, but the timing of the failed tests and the change in localizer between PR's seems to be pointing to this.