Skip to content

Remove Tokens from public API #108

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
Aug 21, 2021
Merged

Remove Tokens from public API #108

merged 1 commit into from
Aug 21, 2021

Conversation

atifaziz
Copy link
Collaborator

I am not sure what the purpose of exposing Tokens was (perhaps for unit testing?), but it doesn't seem to add any value or abstraction to the public API and could add burden for on-going maintenance. With this PR, I'd like to recommend removing it from public visibility before the next release and going 1.0.

@atifaziz atifaziz requested a review from voieducode August 21, 2021 13:42
@voieducode
Copy link
Member

I think the idea was to use this from T4. So it shall not be missed.

@atifaziz
Copy link
Collaborator Author

I think the idea was to use this from T4. So it shall not be missed.

I see. I did check the T4 templates and didn't see any Docopt inheritance going from where the protected overload could be invoked. Anyway, thanks for approving and will merge shortly.

@atifaziz atifaziz merged commit 0c16d50 into docopt:master Aug 21, 2021
@atifaziz atifaziz deleted the x-tokens branch August 21, 2021 14:43
@atifaziz atifaziz added this to the 0.7.0.0 milestone Dec 3, 2021
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.

2 participants