-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Reapply+bugfix: goals with custom props (#5936) #5944
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
Conversation
0d14975 to
8e38748
Compare
|
Is there any meaningful difference between custom props being I see that new goals will default to empty map when created via Elixir, but the same default is not set in postgres. I don't know, just having the same state represented in two different ways creates the need to account for both which seems unnecessary detail to have to deal with. Why don't we set the field to Sorry I missed this in review as well :( |
|
I think the difference is how unique constraints are firing. I dislike nullable columns too. Let me try to run this on top of another migration then |
This reverts commit 8e38748.
Pull request was converted to draft
|
Done via #5946 |
|
Reapply #5936 with some anti-nil defences