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
Standardize star channel usage #815
Comments
Reviewing the source I have found that a public document has a |
|
Thanks, that clarifies.
|
Improving/standardizing the docs is part of the motivation behind this ticket. |
The use case from #787 should be included when considering how we refactor. |
There are three separate special channel concepts, two of which use the same symbol. Internally in Sync Gateway they are referenced by the following constants:
Below are the external touch points for each of these concepts: ! (all users are automatically granted access to this channel)
* (all docs are automatically assigned to this channel)
* ('all accessible channels' selector)
|
Thanks for documenting the usage. I don't think we need any code changes here - just better documentation of the expected usage. In an ideal world we might deprecate the use of At this point I think this just needs to get turned into documentation - assigning to @zgramana for confirmation. |
Agree. For now, I'm marking this as a 2.0 issue, but expect after we think through this it might break into new issue[s]. |
There continues to be confusion between the usage of the
*
channel from the document perspective (as an "all docs" channel), and use of the*
channel as a wildcard (e.g. when filtering channels in a _changes request).Need to refactor the usage to avoid this confusion and standardize the handling from an end user's perspective.
The text was updated successfully, but these errors were encountered: