Yes, it was me that asked this question. Could this be reported as a bug?
Okay, thanks. I was hoping that there would be a way for me to avoid "magic" strings in my code. For example, I would rather write this:
L[MyApplicationResource.Companies.ConfirmDelete] which relies on nested static classes with const string properties,
than this:
L["Companies:ConfirmDelete"] which relies on the same "magic" string appearing in my localization JSON files.
Can somebody whos is resonsible for the commercial modules architecture/design tell me how they intend to avoid the problem of "magic" strings? A large application could easily accumulate lots of bugs over time without a way to make the localization more strongly typed. Can this be made into an official feature request?
At this stage is the 1st bug: It doesn't actually open the Authority Delegation modal dialog. Instead, it simply navigates to the user account screen. See attached video:
The blazor server uses a hybrid UI, so it will navigate to the MVC UI.
I will check other problems and fix them.
So you are saying that this is by design? How can that be right? The functionality is clearly broken.
This was previously reported here: https://support.abp.io/QA/Questions/5464/Issues-when-upgrading-from-703-to-730