-
Notifications
You must be signed in to change notification settings - Fork 53
enforce name uniqueness and pathability. unify section_div approach #1024
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
Conversation
|
Just realized I forgot to update the NEWS file, I will do that tomorrow. |
Unit Tests Summary 1 files 28 suites 1m 45s ⏱️ Results for commit c6a5a9e. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 088bddb ♻️ This comment has been updated with latest results. |
Code Coverage SummaryDiff against mainResults for commit: c6a5a9e Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Melkiades
left a comment
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.
Thank you @gmbecker for the PR!! It looks very good. I was thinking that we could make an addition to the vignette documentation showcasing the new/correct use of section_div and pathing. What do you think? Can be also a very small addition.
We could meet for an overview of the modification and additions. Wdyt @shajoezhu?
Could you check the lintr output too? It is only small things.
|
Hmm thats weird, I didn't commit until I had a clean local lint, I'll try updating lintr and running it agian and see if I can catch the ones that are tripping up the job there. If you're happy with the PR we don't need to meet, but it ended up being more sizeable than I had expected/told Joe it would be so I'm happy to walk you through it if desired. I can look at writing something into the vignette but I'm pretty crunched on time as we're in the process of opensourcing stuff on our side. |
|
ugh, I updated lintr and it noticed some new things, but now I'm back to not being able to reproduce the lint results. its clean locally |
|
hi @gmbecker , I was wondering whats your lintr version? |
|
It was old but I just updated it today in the process of prepping the
second commit. It found issues my old version didnt but still doesn't match
the one in the job apparently 😕
…On Mon, May 19, 2025, 6:02 PM Joe Zhu ***@***.***> wrote:
*shajoezhu* left a comment (insightsengineering/rtables#1024)
<#1024 (comment)>
hi @gmbecker <https://github.com/gmbecker> , I was wondering whats your
lintr version?
—
Reply to this email directly, view it on GitHub
<#1024 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG53MLZLC5B3HV4UFM547327J5KZAVCNFSM6AAAAAB5M3EMUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOJSGYYTANRTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@gmbecker it seems all a matter of indentation mismatch. Using {styler} should solve these issues. Spelling can be fixed too with the {spelling} package update |
|
@Melkiades @shajoezhu styler and lintr are disagreeing: |
|
reverse dependency check works ok https://github.com/insightsengineering/rtables/actions/runs/15151109225 |
|
@Melkiades @shajoezhu I would like adding to the vignette to be a separate issue which I can try to address in time for the release in early June but should not be a blocker for the release, as I did write pretty extensive docfiles for the various new bits. Does that work for you? I think everything else has been addressed besides the annoying |
I will take a look at the lintr issues. Besides for users, the vignette could be helpful also to discern new intended behavior and facilitate reviewing. This PR grew to have many features and changes, and it is a bit hard to keep track of them. Multiple smaller PRs are usually faster to review. Also snapshot testing with clear prompts could help reviewing too ^^. Joe and I are on it anyway!! |
|
hi @gmbecker , the PR looks good. We can come back for the vignette, once the spell and lintr issue is fixed, we can merge it in |
I didn't expect it to get this large either, and I could have separated the section_div stuff out, I suppose, but it seemed natural to have them together and I wasn't sure wed have time to do both. I think the tests I added/changed should give a pretty complete picture of the intended behavior. I appreciate you guys working with me on this! :) |
shajoezhu
left a comment
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.
lgtm! thanks @gmbecker , lets come back for the vignette
|
downstream breaking change fixing in insightsengineering/autoslider.core@91393bd |
This... ended up being more sizable than I expected to get all the behavior fixed and unified. Should be nearly backwards compatible with the exception of behavior that was buggy or otherwise incorrect before.
We should probably meet so I can walk you through this, but I'm happy to discuss on here instead/in addition.