Eventuras v3.0

[losolio]

An issue to make some notes on what is happening towards the upcoming v2.0 release

• Remove Eventuras.Services.Google.Recaptcha, Eventuras.Web project and tests for it. #614
• Obsolete methods will be removed
• We should do some considerations on unused code in the solution
• Remove Eventuras.Services.Google.Recaptcha
• Check if Eventuras.Services.Auth0 is used anywhere, and consider removing the project
• Remove SuperAdmin role
• Change from html to markdown all over
• Consider having different levels of organization settings: public, internal, secret
• Consider splitting name to first and last name, including migrations script to split names
• Consider guid´s for everything in addition to id

[yura-b]

We need to consider using mapping tool, or implement our own reference handler for manual mapping

We have severe duplication of DTOs for each model, depending on what controller is used in request.
For example the Registration domain model has three dtos, each containing same set of information:

• RegistrationFormDto
• OrderRegistrationDto
• RegistrationDto

This duplication makes refactoring and adding new features harder, because you need to support each of those DTOs for tests, add new features in each of them and don't forget any.

However, in current shape of the project, reusing the same DTO will not be possible due to cyclic references (RegistrationDto has OrderDto -> OrderDto has RegistrationDto -> infinite cycle).
With manual mapping, as it is used rn, we need write reference handler, to resolve cycles. Also we need to specify either IgnoreCycles or PreserveReferences on JSON serialization (global setting on startup).
To not write reference handler and simplify manual mapping we could use mapper tool (AutoMapper, Mapperly, etc). However they need fine tuning to work correctly.