-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
ISSUE-72: datafy/nav extensibility for arbitrary Python objects #73
Conversation
I'm not crazy about having to resort to strings for this dispatch but not sure how to do this dynamically otherwise! |
@cnuernber let me know if there are other types I should include. I got |
Also |
This looks good but I am concerned the nav support isn't perfect (which honestly isn't a blocker - one step at a time). Have you tried this in the rebel data viewer? It is a bit hypocritical for me to ask this since I didn't test the metadata pathway in Rebel.... Aside from the above, do you feel this PR is ready to land? Maybe we can file another issue about Rebl and leave it there, thus landing this and moving a bit forward. |
This may have been a lack of imagination on my part. I'm not sure what is worth nav'ing in the standard library. I'll look into it |
…nto ISSUE-72-datafy-nav
Tested that datafy/nav seems to work with modules on REBL. I'm not an expert on REBL so perhaps we can make a seperate issue for testing that. Recommend merging this and creating separate issue for REBL testing. |
Closes: #72
e.g.