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
Fix #45: Thread first changes the indentation of the inner forms #344
base: master
Are you sure you want to change the base?
Fix #45: Thread first changes the indentation of the inner forms #344
Changes from 1 commit
1dfbc99
65e8156
b400730
e3c2e78
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.
Instead of
adjust-idx
which doesn't convey why the index is being adjusted, perhaps instead we just split out the predicate:Then we could write:
I'm unsure why you have
(some-> dec (max 0))
instead of justdec
. Under what circumstances would the index be less than or equal to zero?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.
Wouldn't
idx
be zero in this case, if I configured{cond-> [[:block 0]]}
?There is a check for
(nil? idx)
ininner-indent
already. Isn't it nil when there is no indentation rule, like(-> x foo bar)
?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.
The index is the position of the child in the parent form, IIRC. So, come to thing about it, we could change
(not (first-argument? zloc))
to(> idx 1)
.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.
Doesn't the index come from the :indents as specified here?
So for
:block
it uses default indenting until we reach the index. So if we are in a thread, we should basically hit that index one spot before (ie. decrease the index). If the index is 0, we should keep it at 0.For
:inner
when index is set, it is restricted to that particular index. So that should also occur one spot earlier (ie. decrease the index). If the index is 0, then we should avoid using this indentation rule, since the spot it was meant for is not present.I also oversaw the
depth
argument of inner. Here we should check whether the parent of thetop
zloc is wrapped in a thread. I'll commit a fix.Hope it makes sense.
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.
Ah, yes, I believe you're right. I need to refresh myself on the indentation logic as it's been a while since I've looked at it.