Fix for False Identification of an Interaction on LHS in mold()
#174
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
Member
|
@ddsjoberg thanks! We really appreciate your contribution. However, I've decide to solve this a different way over in #175, so I'm going to close this PR. Thanks again! |
Author
|
Thanks @DavisVaughan ! I am sure your solution is much much much more robust! I'll keep an eye out for the next release of the pkg 🕺🏼 🕺🏼 🕺🏼 |
|
This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pull Request closes #173
Fix allows users to use a package prefix for a function on the LHS of the formula in
mold(), e.g.mold(survival::Surv(time, status) ~ age, data = survival::lung)Previously, the code checked for a colon in the terms. I updated it to use lookahead and lookbehind regular expressions to search for a colon that is neither preceded nor followed by another colon.
Thank you