Breaking changes in PropertyMapping<T>? about fastcrud

[MoonStorm]

Yes, version 3.0 has introduced some breaking changes.

In the area you mentioned, I believe the goal was to remove the informational properties in favor of the fluent registration methods. Both in there just made a mess. But yeah, I agree with you, exposing the mapping info shouldn't go away. We'll have something done in the next minor release.

[the-black-wolf]

You can leave the fluent stuff as it was added (its good architecture choice), but just convert IsPrimaryKey to a getter only property, that will allow discovery and prevent properties from messing up the fluent chain. Do that for other stuff also.

[MoonStorm]

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.