Upgrading from Intent.Security.JWT 4.2.5 to 4.3.1 doesn't create CurrentUser record

[LiamJG26]

What happened?

I upgraded the module and I then had a compile error in Project.Api/Service/CurrentUserService.cs:

I looked through the module source code and saw that it was supposed to add a CurrentUser record. I deleted the CurrentUserService.cs and then ran the software factory and it generated correctly:

Initial change:

Change after deleting CurrentUserService.cs:

This was part of a pretty big upgrade that also required reinstalling 2 modules due to template registration error I received when running the software factory. I don't remember what those 2 modules were though.

Ultimately this is not an issue anymore but it seemed to point to a bigger issue with the generation of certain parts of code.

I've attached my old CurrentUserService.cs, old modules config and new modules config in this zip file if that helps:

CurrentUserService.zip

How is This Issue Affecting You?

✅ I have a workaround, but a fix would be ideal (Minor)

What version of Intent Architect are you using?

4.5.14

Additional information

No response

[jp-seini]

Hi @LiamJG26

Apologies for the inconvenienced caused, and I'm glad you have a solution. Appreciate all the information you provided.

It seems to be related specifically to adding the record to file-scoped namespaces - it works when not a file-scoped namespace. I have this logged as a priority.

As you have mentioned, in the short term the workaround is to delete the file and have the file generated from scratch again, or to install the updated module, but before running the Software Factory, change the file non file-scoped namespace. Then run the Software Factory and the record is added, and the file is changed back to file-scoped.

Please do let us know if you run into any other issue, and we'll try address them asap.