[#150] Research whether we should create different types for each element (DTO, struct, Props etc..) in parser, or whether this should be done in the semantic analysis step (intermediate model validation), while keeping one type in the parser.
If a validation step is introduced, the model types should be more specific, for example create of entity will expecter a props type, and not a BitloopsPrimaryType, so we will avoid all these redundant type checks
if(BitloopsPrimTypeIdentifiers.isArrayPrimType(propsName)){thrownewError('Array is not supported as entity props type');}
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Originally posted by: ellik95
domainCreateEntityMethodwithdomainCreatemethod which is similar (only the constructor changes)Originally posted by: Varagos
[#150] Research whether we should create different types for each element (DTO, struct, Props etc..) in parser, or whether this should be done in the semantic analysis step (intermediate model validation), while keeping one type in the parser.
If a validation step is introduced, the model types should be more specific, for example create of entity will expecter a props type, and not a BitloopsPrimaryType, so we will avoid all these redundant type checks
Originally posted by: sardounis
File dependencies do not have clear API and they are used in multiple places
Originally posted by: sardounis
Create specific classes for:
Originally posted by: sardounis
add tests for dependencies (toTarget)