Lambda-like support for callbacks#33
Conversation
Added rich callback support for callbacks. This should still keep most of the uses still working except the ones with spaces in them. Also adding more documentation for the above feature.
Some checks didnt pass because i used the f"{varName=}" syntax for testing. So commenting those lines out!
|
Huh. the "workflow tests" failed because I used |
|
Now I remember why I avoided type hinting. It is always changing and not consistent. Your code only works for 3.10 because of the type hinting. |
|
I would recommend you drop all type hints for now |
see; I wont drop ALL type hinting; I would like to keep some basic type hinting for sure. Again; pushing a commit... |
Removed some type hinting because of runtime errors on older versions of Python.
Made the implementation better, faster, and smaller in size by using a helper function called `parseHelper` which just returns the args and kwargs it recieves.
New docs for the new implementation.
changed camelCase to snake_case for consistency. Also, removed unnecessary functions.
Maintainer asked to not make docs myself.
This commit acknowledges some of @ObaraEmmanuel in pull request ObaraEmmanuel#33
There was a problem hiding this comment.
I have polished up the code. It still does not pass some of the lambda tests I have written locally so I will add some more code to resolve this later in the week. I also intend to change for format from funcname arg1 arg2 ... kwarg1=v kwarg2=v ... to funcname(arg1, arg2,..., kwarg1=v, kwarg2=v, ...) for easier parsing.
This commit acknowledges some of @ObaraEmmanuel in pull request ObaraEmmanuel#33
2 participants
Added rich callback support for callbacks. This should still keep most of the uses still working except the ones with spaces in them.
Also adding more documentation for the above feature.
Issues resolved: #32