return nil for relationships that exist but are empty #11
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.
in cases where a relationship is possible (e.g. an
ApplicationForm
can have anApplication
) but it doesn't exist for a specific instance, we should just returnnil
when trying to access that relationship (e.g.application_form.application
should just returnnil
if there isn't anApplication
, instead of throwing an error), which is the behavior with ActiveRecord