Do not ignore the default
option for collection attributes
#37
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.
I noticed that the
default
attribute option is ignored and replaced with-> { [] }
for collection attributes.I find it annoying, especially when someone wants the collection to be
nil
by default. Because thedefault
option is disabled it is very hard to achieve.I modified the behaviour so that collection attributes replace the default proc with
-> { [] }
only whendefault
isnil
.This preserves the original behaviour of collection attributes having an empty array by default when no
default
option is passed. But the provided non-nildefault
is respected.