In PiExampleFluent the fluent code starts like this:
Generate
.MethodImplementation<int, int>()
However, this is not intuitive. You can't tell which generic type argument is the return type and which is the argument. Thats why, in the new Mapper class there is a new flue API example:
Generate
.Method().WithParameter<FourLeggedAnimal>().WithReturnType<MammalAnimal>()
Implement it. Replace the old way with the new way (both here, other examples, and in tests).
Remove the old way, the package was not released yet so no need to ensure backwards compatiblity nor Deprecated attribute. Just remove the old way and relpace all usages with the new way.
Also, ensure the new example works, create something similar for tests.
In PiExampleFluent the fluent code starts like this:
However, this is not intuitive. You can't tell which generic type argument is the return type and which is the argument. Thats why, in the new Mapper class there is a new flue API example:
Implement it. Replace the old way with the new way (both here, other examples, and in tests).
Remove the old way, the package was not released yet so no need to ensure backwards compatiblity nor Deprecated attribute. Just remove the old way and relpace all usages with the new way.
Also, ensure the new example works, create something similar for tests.