Closed ChrisPulman closed 1 month ago
What kind of change does this PR introduce?
Fix for #9
What is the current behavior?
ReactiveCommand generated name follows the name of the method
What is the new behavior?
ReactiveCommand generated name follows the name of the method but allows for: Name(), name(), m_name(), _name()
generating NameCommand
What might this PR break?
previously generated names would have followed the method name
Please check if the PR fulfills these requirements
Other information:
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What kind of change does this PR introduce?
Fix for #9
What is the current behavior?
ReactiveCommand generated name follows the name of the method
What is the new behavior?
ReactiveCommand generated name follows the name of the method but allows for: Name(), name(), m_name(), _name()
generating NameCommand
What might this PR break?
previously generated names would have followed the method name
Please check if the PR fulfills these requirements
Other information: