-
Notifications
You must be signed in to change notification settings - Fork 48
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
1087 feature add ability to assign legal entitycompany as organizer #362
1087 feature add ability to assign legal entitycompany as organizer #362
Conversation
Coverage report
Test suite run success180 tests passing in 64 suites. Report generated by 🧪jest coverage report action from d9c3a0b |
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.
Once again an awesome contribution @dimitur2204
I can't see anything that can be improved around the code.
In your question - we're using toEntity
so we can encapsulate which field are used to connect to external entity in the db. We validate the input uuids and link them annoyingly to reduce the duplication and reuse the code. The relation objects are a pattern that we couldn't validate enough to make sure we're consistent with it everywhere. The other approach seems to be more simplistic for the time being as the frontend doesn't have to know the proper json to match the Prisma linking style.
Purpose
Add
company_id
field on the campaign regarding #1087 with a relation to the company field.Notes
I noticed that sometimes we have these Relation objects and sometimes we don't
Here we have it:
And on this PR for example for the
campaign
we instead have atoEntity()
function that seems to connect the fields:Is there a difference?