MoonStorm
MoonStorm
We appreciate the PR and played around with the idea a bit, however at the moment we think that this is outside the scope of the library. I'm sure we'll...
Added customizations for both the class and the property modifiers. Also added a warning pragma for CS8618.
It has finally stopped working for me as well. I'm assuming it's a problem between .NET Core and the Intellitrace implementation in Visual Studio. Either way, the best way to...
For now it's back in there but marked as Obsolete but without erroring. We'll find a way to bring them later in a different form.
Playing around with it more, I don't believe assigning entities to schemas from the generator is a good idea. Entities can be tweaked later if needed.
Decided to add the feature as an opt-in flag so it won't break existing generations. The flag will set the Schema property in the Table attribute. See #198
Yup, the `Schema` property inside the `Table` attribute should be used. There is another open case that might prevent the schema from being used properly. I'll take a look.
Should be fixed in 3.3. Give it another go please.
I honestly don't expect the model generator to solve all the situations. I usually have my entities done code-first before I start working on the DAL. Btw, just added a...
It looks like it. The list of open issues keeps on growing, same as the pull requests nobody's looking at. The generator is filled with hundreds of options which amazingly...