Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat/refactor: dedicated classes for texts and inline comps #356
feat/refactor: dedicated classes for texts and inline comps #356
Changes from all commits
07dbaf8
8260c32
8d2b697
6050b06
ac1552f
1c5844c
383b541
cf955ff
9e48f81
61a429f
935995e
4b8f1ec
a2034a2
3c8c5b4
f55e26f
dc56572
2d00a01
f2d462a
6d17ed5
e2d7756
9524c6a
b274d05
05b26c1
f4080c3
e1957ed
a71c475
d17f8ba
4b0f3d3
7e8d370
9b47593
8ac088c
c6ea598
d1aa000
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you considered property renaming in this context? I.e., does your code exhibit well-defined behaviour for when a property is present in a parent, but also in the entity itself (but possibly with a changed type)?
As of today, this is a known restriction. Even if you do not explicitly solve the issue, this could be an opportunity to error out if we find redefined properties.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I haven't considered them - why would anyone do that 😶🌫️. No proper solution comes to mind right away, I would have to think about it some more.
If I understand you correctly I could implement the following approach though, to error out and stop the type generation in case of a type mismatch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know what the architectural reasons would be, but it has happened in the past. 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P.S.: I asked this mainly out of curiosity. As it is beyond the scope of your PR, this can totally be done at a later point in time and by someone else.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I would actually table this for later if this is ok for you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely! 🙂