Open
Conversation
Also add tooltip with the method signature, pretty print the method name ( doThing() -> Do Thing ), and make method buttons that do have parameters use any default parameters in the invocation foldout too.
Author
|
Remade the pull request with only the intended commit. |
Author
|
Do let me know if I can provide anything to help get this merged. Happy to update docs for it if you find the features useful. |
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 free
to 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.
Pretty prints method name with

ObjectNames.NicifyVariableName(), and adds the method signature as a tooltip:Allows displaying a button with parameters as a simple button instead:

This will use default parameters when those are specified in the method signature.
Also fills default parameters when specified, for the normal invocation foldout:

Some other areas I'd like to improve and may get to:
I haven't tested this extremely thoroughly yet, and obviously there should be a documentation update alongside these changes.