- Notifications
You must be signed in to change notification settings - Fork15
[EXPERIMENTAL] Add "onchange" hook#262
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Draft
eriknw wants to merge1 commit intopython-graphblas:mainChoose a base branch fromeriknw:hooks
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Draft
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or 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 freeto 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.
This is a PoC to see how invasive it is to add "onchange" hooks.
Theremay be two uses for this from
graphblas-algorithms
:A
to the user.Overall, I'd say this isn't very invasive all things considered. The number of places hooks are in each file is:
This hook system is pretty simple for now. It only has one hook,
"onchange"
, and it only passes the object that would be changed to the function. Other hooks and arguments to pass to the callbacks are possible (hence our use of**kwargs
in the callback for future compatibility). This also doesn't try to manage having multiple callbacks, which is fine for our current use cases where the objects with hooks will be managed bygraphblas-algorithms
.We may want to add a simple API to manage hooks such as
_add_hook
,_has_hook
,_call_hook
, etc. to make it easier to evolve.We can let this stew for a bit.