Skip to content
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

Upkeep #79

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Upkeep #79

wants to merge 8 commits into from

Conversation

dunkenwg
Copy link

No description provided.

@dunkenwg
Copy link
Author

When I run the check/documentation for this package I get:

══ Documenting ══════════════════════════════════════════════════════════════════════════════════════
ℹ Updating embr documentation
Writing NAMESPACE
ℹ Loading embr
✖ pars.R:105: S3 method `pars.character` needs @export or @exportS3method tag.
Writing NAMESPACE

Should pars.character() be exported?

Copy link
Member

@joethorley joethorley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you talk to Ayla when she is back about the NOTE around exporting S3 tags? I don't think it should be exported as it will likely break things in this case but we should suppress the NOTE if we can.

@dunkenwg
Copy link
Author

Can you talk to Ayla when she is back about the NOTE around exporting S3 tags? I don't think it should be exported as it will likely break things in this case but we should suppress the NOTE if we can.

I'm also going to wait until Ayla is back to discuss why the Mac OS R-CMD-check is failing due to a segmentation fault as I'm quite lost.

@aylapear
Copy link
Member

Can you talk to Ayla when she is back about the NOTE around exporting S3 tags? I don't think it should be exported as it will likely break things in this case but we should suppress the NOTE if we can.

This seems to be a new thing the documentation is requiring us to do. For now ignore the issue as we are working out what to do for this across the board. Please make an internal-infrastructure issue about this and list this repo in the comments and once we figure out the appropriate fix we can apply it to the relevant repositories.

@aylapear
Copy link
Member

I'm also going to wait until Ayla is back to discuss why the Mac OS R-CMD-check is failing due to a segmentation fault as I'm quite lost.

I am not familiar with this specific issue, give me a call next time you are working on it and we can chat through some things to test to dig into the issue further.

Copy link
Member

@aylapear aylapear left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good but we need to figure out the failing action before we can merge in the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants