🚨 fix: coherence within associations fields authorization #3687
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.
Description
Fixes #2614
read_only
anddisabled
options were interfering with the rendering of attach/create buttons onhas_one
fields, while not affecting other association fields such ashas_many
.We decided to remove these options from the attach/create functionality to maintain consistency with other fields, and now attach/create is controlled solely through authorization (attach_{association}? / create_{association}?).
🚨 Breaking Changes
Heads up:
read_only
anddisabled
don't affecthas_one
fields anymore.Please search for all
has_one
fields still using theread_only
ordisabled
options and update them with the correct authorization methods: attach_{association}? and create_{association}?Checklist: