-
Notifications
You must be signed in to change notification settings - Fork 256
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
Return type annotations for vedo functions #1089
Comments
Hi Johannes! sure i'm completely open to the idea. |
HI @marcomusy, thanks for the hint, I totally hadn't seen it, cool work! I think the current return type annotations ( Also, did you just give me some sort of semi-maintainer status? 😲 (I cannot see my level of permissions) |
Fantastic. I will probably update what I did with the Yes I added you to Collaborators so you can push directly any changes (i think you are a vedo expert by now!) |
@marcomusy thanks! Will proceed with a few type annotations next then. Napari has a few issues deciphering whether some inputs are supposed to be floats, integers, etc. |
Hi @marcomusy ,
long time no hear :) I'm still low-key working on the idea I pitched to you last year August at the NEUBIAS conference in Dresden, which basically revolves around harvesting all vedo functions to be automatically wrapped for usage in Napari. This would be awesome because
I have some sort of a working version, but what's making my life a bit hard is the lack of type annotations in vedo, specifically return type annotations. For starters, I wanted to limit myself to harvesting functions that take a mesh as input and return another mesh (as opposed to functions that color a mesh, or measure something on the vertices, etc).
What would make my life much easier, would be, instrad of vedo mesh functions being defined like this
but rather like this:
The return type annotation in the latter case could be used to mark functions that do return meshes and nothing else. Similarly, functions consuming a mesh and returning a pointcloud could be annotated like this:
Would you be (in principle) be open to such changes? I would take the PR writing to myself, of course :)
The text was updated successfully, but these errors were encountered: