Add initial channel structures #211
Merged
Conversation
This file contains 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
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.
What does this change?
Add the initial structures to support content channels. These will likely grow over time but for now, this is the minimum we need to get started.
How to test
We'll build and release a local SNAPSHOT for local testing, then potentially make a beta release version for CODE testing before a final release for PROD.
Update:
Most recently released as
17.6.0-beta.1to maven and npm. Have tested with that build.How can we measure success?
These effects will become visible in CAPI output at various points during testing.
Have we considered potential risks?
Risk is very low. We're adding data so any consumers of prior versions will be none the wiser anyway.
Images
N/A
Accessibility