Closed mstahv closed 5 years ago
To me firing events sounds like normal developer jargon, but as you wish. I'll modify the change a bit.
To me firing events sounds like normal developer jargon, but as you wish. I'll modify the change a bit.
It's definitely a normal jargon.
The problem is that the click
method executed via JS is something more than firing an event. So the method name is confusing since it does something else.
As a side note: fireXXX
methods are not normally exposed as public
. They should be private methods which are not visible to the end developer. There always should be a meaningful action which changes a state and as a result fires an event about this state change.
There are merge conflicts that need to be resolved.
SonarQube analysis reported 2 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:
closes #67
This change is