-
Notifications
You must be signed in to change notification settings - Fork 27
Check License on Entry Get #369
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
base: DLAPI-563-licensing
Are you sure you want to change the base?
Check License on Entry Get #369
Conversation
| }, | ||
| }, | ||
| licenseAssignment: { | ||
| relation: Model.HasOneRelation, |
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.
Looks like ManyToMany
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.
In this context the result can have only one LicenseAssignment. Something similar we have with Favorites
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.
Presentation would be more transparent in this case ;)
| licenseAssignment?: { | ||
| licenseAssignmentId?: string; | ||
| expiredAt?: string | null; | ||
| licenseType?: string; |
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.
- We have
LicenseTypeenum. - Why all fields are optional?
| }, | ||
| }, | ||
| licenseAssignment: { | ||
| relation: Model.HasOneRelation, |
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.
Presentation would be more transparent in this case ;)
No description provided.