-
Notifications
You must be signed in to change notification settings - Fork 1
WIP: Namespaced AppContext
#16
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should expose the autogenerated key to the user at all. Why not just deal in the string options?
I'd be fine with that. I can take out that part of the docstring so the only way we tell users to use the |
with opts.inserted_options(): | ||
default = MyCustomData(10) | ||
data = appctx.get('solver_custompc_somedata', default) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
split this docstring.
with opts.inserted_options(): | ||
default = MyCustomData(10) | ||
data = appctx.get('solver_custompc_somedata', default) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please create an issue describing what was discussed in the meeting about global options prefixes. I'd have loved to say more but my wifi was terrible!
Co-authored-by: Connor Ward <c.ward20@imperial.ac.uk>
Corresponding Firedrake PR: firedrakeproject/firedrake#4526