Decide on a naming standard for event objects

[Pikachu920]

I think we should add a naming standard for how we name event objects. Some contributors use e and others use event. I think we should probably find a standard before this inconsistency continues to grow in the codebase.

Related PR: #4992

[Pikachu920]

Copying existing discussion from #4992:

[Moderocky]

Just following up on my original comment, I'm in favour of event (and avoiding one-letter names for complex types in general.)
I explain my reasoning fully in my style guide here but the quick version is:

• Most people use single-letters for primitives (int i, boolean b, char c) and it helps not to get confused.
• You can always know what the variable is when reading a large code block e.g. on GitHub.
• Giving a parameter a good name is like a mini-documentation suggestion of what it's supposed to do.

[TheLimeGlass]

Should be event

You should always be using proper naming and not short cutting.
Developers can understand what event is without knowing the object is Event.

As Elon Musk tells SpaceX all the time "Stop, using, abbreviations! It makes it harder for the newer intern to understand."

[Itzdlg]

Don’t know if I should upvote-react a similar answer instead, as I don’t know how this’ll be decided, but I agree with Kenzie. Using event is proper & more verbose, especially when there could be any number of types for e like expression or exception.