-
Notifications
You must be signed in to change notification settings - Fork 496
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
Cleanup documentation code #981
Conversation
9ce3746
to
605b365
Compare
anyone seen this error before |
I haven’t. |
I think it has to do with internal packages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with comments
Why does internal need to have its own module? You can just name the folder as internal and it will not be exposed https://dave.cheney.net/2019/10/06/use-internal-packages-to-reduce-your-public-api-surface |
I'm not sure why I'm unable to compile. If I If I If I import If I import Thats' why I was creating a module, which seems wrong. |
problem solved. The package name was different from the folder name. I've learned my lesson. |
93edf14
to
0d529b4
Compare
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature/fix
What is the current behavior? (You can also link to an open issue here)
documentation code exposes all internal APIs and check documentation URL not present in JSON.
What is the new behavior (if this is a feature change)?
The
docs/
folder contains code that is exported by default. This PR:Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
yes
Other information: