Skip to content

Don't export LayerSf #3208

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

Merged
merged 1 commit into from
Mar 27, 2019
Merged

Don't export LayerSf #3208

merged 1 commit into from
Mar 27, 2019

Conversation

thomasp85
Copy link
Member

Fix #3158 This will undo the export of LayerSf

@thomasp85 thomasp85 requested a review from clauswilke March 27, 2019 18:38
Copy link
Member

@clauswilke clauswilke left a comment

Choose a reason for hiding this comment

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

I think this is fine, but @yutannihilation should sign off on it too.

@thomasp85 thomasp85 merged commit 14a39c2 into master Mar 27, 2019
@thomasp85
Copy link
Member Author

I'll merge it now as it may otherwise be lost in the process... the layer_type argument is something we can have another time I think...

@clauswilke
Copy link
Member

I’m more concerned that we have unexported LayerSf but haven’t added layer_sf() yet. This may have downstream implications for packages under development, e.g. ggrepel. @yutannihilation is the person most likely to have such code floating around somewhere.

@yutannihilation
Copy link
Member

Thanks for mentioning me! I think it's fine not to add layer_sf(). We can add it when we get sure it's needed.

One thing, do you think we can remove layer_class argument of layer()? Though this argument is visible to users, this is not usable because no Layer class is exported.

show.legend = NA, layer_class = Layer) {

It's not necessary but nice if we can remove this to avoid confusion.

@yutannihilation
Copy link
Member

Ah, sorry I missed this comment: #3207 (comment)

OK, let's leave layer_class and do this:

We could add "for ggplot2 internal use only" to the documentation to make this clear.

@lock
Copy link

lock bot commented Sep 23, 2019

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Sep 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Don't export LayerSf
3 participants