scaffolding | scaffolding is a very pointless esolang

I would recommend you to not mix these two things. With reverse engineering, you will get a generated DB context class file, but with the code first approach, you are manually writing the context file.

Why do you want to use reverse engineering? If you want to create the entity classes for the views from the DB, you can use it, but in my opinion this is not so comfortable (you should only keep the changes that are related to the views and drop everything else).

It is a known problem about compile multi-module program that contains TH code for profiling, see related sections in the documentation:

This causes difficulties if you have a multi-module program containing Template Haskell code and you need to compile it for profiling, because GHC cannot load the profiled object code and use it when executing the splices.

As a workaround, just put TemplateHaskell into the other-modules in your test.cabal,

You don't have to replace the jsdelivr, that piece of code is fine; also I think you need to reorder your code a little bit:

• You should put the faceMesh initialization inside the useEffect, with [] as parameter; therefore, the algorithm will start when the page is rendered for the first time
• Also, you don't need to get videoElement and canvasElement with doc.*, because you already have some refs defined

An example of code:

Did you inherit from IdentityDbContext? :

The issue was because my use of using System.Text.Json.Serialization; in the startup to utilize ReferenceHandler.Preserve for a looping issue - that I'm still not sure I fully understand

Regardless - removing this resolves the issue

Don't call your class DbContext. You can't have a class with the same name as the base class. A better name would be TechTestDbContext:

If you use Azure, yes key vault is one of the way. Other cloud services provided similar services for secret management.

The strategy would be to implement some sort of caching in memory the first time you read from key vault/secret provider. That way it will reduce the time to get that connection string every time next time or another part of your code want to access the same connection strings.

You can expire the cache so you can kind of reload the connection strings or secrets from the key vault if you would like, it is up to you at the end.

To conclude this ticket I discovered that 3.1 does not scaffold hidden fields when the compatibility level is equal or greater than 130.

In entity framework 2.1 it checks the server version (equal or greater than 13) instead of the compatibility level.

In our case we were running Sql Server 2016 (version 13) but with a lower compatibility level (120). Once we updated the compatibility level to 130 the hidden fields no longer were scaffolded.

These differences can be seen in the following files in the efCore git repo:

efCore 2.1 (line 538) https://github.com/dotnet/efcore/blob/release/2.1/src/EFCore.SqlServer/Scaffolding/Internal/SqlServerDatabaseModelFactory.cs

efCore 3.1 (line 621) https://github.com/dotnet/efcore/blob/release/3.1/src/EFCore.SqlServer/Scaffolding/Internal/SqlServerDatabaseModelFactory.cs

This works in graph_objects