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
Automatically build missing values for valid fields. #6
base: master
Are you sure you want to change the base?
Automatically build missing values for valid fields. #6
Changes from all commits
09c322a
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.
set_dynabute_attributes() for has_many field sounds more like it's replacing the whole values with the given array. having
append_dynabute_value
(which should throw error when called on non has_many field) seems more natural to me, what do you think?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.
My idea was that you have single method for setting the values. It was intended to be like
create_or_update
concept.Just like rails, when submitting a form for persisted object (
id
exists), it will trigger update action. In case the object is not persisted and there is noid
value, form will submit create action and the new record will be added to the database.So first time you call method for
has_many
field, it will add specified value, same as with strings and integers, but it will return an Array. Next set will just append to that Array as something already exists.Let me know if you have something specific on your mind 😉