-
Notifications
You must be signed in to change notification settings - Fork 2
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
Sundry config fixes #776
Sundry config fixes #776
Conversation
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.
a couple suggestions for simplifying the logic in the new macro slightly, and i'd lean slightly towards testing the small part of the code that seems responsible for the coverage drop. but otherwise, looks fine to me, thanks for all the iterating and updating!
also @jacobthill i'm leaving this as a comment -- i went to request changes, but this is technically my PR, even though the work and the commits are all yours, since i did the branch wrangling (and so i'm not allowed to approve or request changes).
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.
🎉 nice, looks good! thanks for the touchups, @jacobthill!
one thing: looks like a little bit of detritus got committed, maybe errant copy/paste on the CLI? see image...
0e53198
to
7558d30
Compare
Why was this change made?
this splits out the traject config and macro changes @jacobthill made on top of the first two commits of #762. since i didn't have any hand in those follow-on changes, and since they are in separate parts of the code changes i made in my first two commits, i can review them separately, and hopefully get this PR merged on its own.
How was this change tested?
CI, running transform locally on laptop
Which documentation and/or configurations were updated?
lots of traject configs