Skip to content
This repository has been archived by the owner on Jan 15, 2020. It is now read-only.

Split public API from internal implementations #363

Open
planger opened this issue Sep 2, 2019 · 0 comments
Open

Split public API from internal implementations #363

planger opened this issue Sep 2, 2019 · 0 comments

Comments

@planger
Copy link
Collaborator

planger commented Sep 2, 2019

A generic point that we should start thinking about is to make it clear (by package name) what is internal and public API meant to be directly used and extended by clients. This will give us more flexibility in the future when doing modifications as we'll know what we can change without affecting existing language-specific client implementations.

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

No branches or pull requests

1 participant