Fix depth calculation for Input arrays #37
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DanielJette
approved these changes
Mar 28, 2018
| _queryBuilder.append(listSeperator#{depth}); | ||
| listSeperator#{depth} = ","; | ||
| #{generate_build_input_code("item#{depth}", item_type, depth: depth + 1)} | ||
| } |
Contributor
There was a problem hiding this comment.
I don't get it. Did you just add a scope to the block?
Contributor
Author
There was a problem hiding this comment.
Yeah, it was being called again in Input.java.erb for the optional fields but had no context to resume the previous depth count. Just added a block so it can safely start at 1 again for new fields.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Limits scope for non-recursive calls.