-
Notifications
You must be signed in to change notification settings - Fork 39
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
Document ContextKeys
#146
Comments
yep. just to reiterate, that doc is not meant to be the place where people go to see the keys in that file. It is not intended to be kept in sync with any specific set of context keys. It's a conceptual document for napari devs to understand what context keys even are, (not a reference for what keys are valid) |
Thanks, I had the impression that these comments in the napari/napari#4499 review were the blocking one, so I opened. this just to be safe. It's easy to close later if we want. Especially since GH now have "close as not planned". |
Could we update the title of this issue to be about documenting context keys (as they are not meant to be documented in We don't currently have a place for context key documentation. We also need to decide if we want to autogenerate the docs and if so, how. ping @melissawm or @psobolewskiPhD (I think you both have rights) |
guides/context_expressions.md
with new values after #4499 mergeContextKeys
Just wanted to update this after discussion with @melissawm at the docs meeting: @melissawm suggested that we could something similar to what is done in Context keys are not exposed publicly yet though. I think we eventually would expose them as part of NAP-6 ( |
From napari/napari#4499,
Originally posted by @Czaki in napari/napari#4499 (review)
@talmbert03 later replied:
As we may have this document auto generated and the plugins do not yet have access to those values, I think we can postpone the documentation update and move forward with the code.
The text was updated successfully, but these errors were encountered: