Make all packages internal #40
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Go packages of this project were written solely for the use within the project. Making them internal avoids them unintentionally becoming part of the public API, which would result in a greatly increased potential maintenance and support burden and limitations on further development work. It would be interesting to eventually evaluate whether any components of the internal API might be useful to others and expose them intentionally as they reach a state of relative stability. However, for now the public API should be considered to be the: - Configuration file format - Index source list format - Library Manager index format
per1234
added
type: enhancement
rsora
approved these changes
May 27, 2021
silvanocerza
approved these changes
May 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Go packages of this project were written solely for the use within the project. Making them internal avoids them
unintentionally becoming part of the public API, which would result in a greatly increased potential maintenance and support
burden and limitations on further development work.
It would be interesting to eventually evaluate whether any components of the internal API might be useful to others and
expose them intentionally as they reach a state of relative stability. However, for now the public API should be
considered to be the: