Delete duplicate beforeValueRender jsdoc

[corburn]

Context

The beforeValueRender event is documented twice, this commit removes one.

pluginHooks.js#L702

pluginHooks.js#L1122

How has this been tested?

untested

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature or improvement (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issue(s):

Checklist:

• My code follows the code style of this project,
• My change requires a change to the documentation.

[AMBudnik]

Hi

Thank you very much for sharing the pull request with us!

Yesterday we have changed the Contributing policy, a new file can be found here. As you can see the first obligatory step is to sign a CLA document that will allow us to check your code and (if it meets project requirements) merge it to Handsontable.

As most of the PR in our repository are 3 months+ old we have decided to close them all and reopen immediately after the author confirms that all the steps of the Contributing file have been accomplished.
In the same time, I am really sorry that we have waited so long to provide the correct pull request process. I hope that now we will be able to build the perfect library together :)

ps. if you have added more than one pull request please share all their numbers in one post. Thanks in advance!

[corburn]

All the steps in the Contributing file have been accomplished.

[AMBudnik]

Thank you, your PR is ready for a review. It will be reviewed as soon as possible.

[krzysztofspilka]

@AMBudnik as a rule of thumb, we should schedule reviews more precisely. In this case, for instance, we can look at this on Friday (or next Friday at the latest). What do you think about such approach?

PS it requires some preparation during a week and a short notice/summary to be sent on Friday to the dev team.

[AMBudnik]

@krzysztofspilka sure! If something isn't scheduled it can hang on the to-do list forever. We can set the 'review' time from one Friday to another, which gives us a full week starting from the point of picking up a PR to actually returning some feedback.

What we should consider though is the fact that one PR can change 2 lines of code like correcting typos in documentation and another can add 10k lines of code and a new feature.

[budnix]

Thanks, @corburn for PR!