-
Notifications
You must be signed in to change notification settings - Fork 2
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
[patch] Add a utility to the API for finding node classes #439
Conversation
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesCodacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
…ersion (nodes with list of all node functions no longer available, therefore a new parser has been implemented)
Pull Request Test Coverage Report for Build 10693654494Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
So we can iterate on it while still making weaker semantic version upgrades
And refactor the boolean flag to be in line with the other two
Per @JNmpi's request pyiron/pyironFlow@679faf3#r146023624
TODO:
demo it somewhere? Maybe the deepdive?It's "hidden" (private) in the API. If the interface settles (next point) we can demo it then.Recursion? Instead of a list we probably want to walk the source and return a nested dictionary.A per-module version is already a step forward. It can be used inpyiron-xyflow
(or elsewhere) and we can migrate walking code here if it gets written.