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

[WIP] Clarify the Use of Public API Methods #212

Draft
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

allerter
Copy link
Collaborator

@allerter allerter commented Jun 5, 2021

This PR makes the use of Public API methods clear to the user and also makes sure the user accepts the risks of the Public API before using its methods.

This PR introduces breaking changes and mustn't be merged until 4.0.0

allerter added 7 commits June 5, 2021 13:19
Since Genius inherits and then initiates its parent objects, we need to add the **kwargs parameter to the init of other objects so that they ignore the allow_public_api parameter.
Made clear in Genius methods docstrings that they use PublicAPI methods.
The same needs to be added to the docstrings of the PublicAPI methods.
@allerter allerter added this to the 4.0.0 milestone Jun 5, 2021
@allerter
Copy link
Collaborator Author

Also, all Public API references (in code as well as docs) should be renamed to Web API. Genius considers its official API to be the Public API and refers to the unofficial API as Web API. Renaming these will create reduce confusion.

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

Successfully merging this pull request may close these issues.

None yet

1 participant