feat(ClientEvents): add tuple labels to event arguments #5225
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.
Adds labels to the tuple types in the ClientEvents interface (typings). These labels will appear as argument names when using IntelliSense, instead of 'args_0', 'args_1', etc. They will be helpful for knowing exactly what each argument represents, mostly in update events (which pass the 'old' and 'new' version of the object), and shard events (which pass the shard ID).
Although most labels are self-explanatory, some other may need slight changes to be more accurate.
Status
Semantic versioning classification: