Establish internal/private.ImageDestination #1462
Merged
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.
Based on the #1439 experiment, this is trying to establish the common type, so that we can then separately work on the client-side wrapper, and the implementation-side compat/helper infrastructure.
This includes some commits from #1439; the new part is a proposal to, instead of using
publicTypes "…/v5/types" and
internalTypes "…/v5/internal/types, with
internalTypes.ImageDestinationWithOptions, to use
types "…/v5/types"(as we used to) and
private "…/v5/internal/private", with
private.ImageDestination`.The “private” name, as well as all other aspects, is certainly open for debate.
See individual commits for details.
@vrothberg WDYT?