Evaluate events to determine whether additional object data can be exposed #2580
Description
What happens now
Some variables in events are hidden / not exposed because they communicate information useful to the developer and weren't anticipated to be useful to the end user.
What I'd like to happen
EDDI users would like more of that data exposed (particularly so that invariant and localized names are both available, rather than having invariant names be hidden).
How it can happen
- Go through EDDI event variables and evaluate whether currently hidden variables can be exposed, paying particular attention to localizable variables or to objects containing localizable variables.
- Consider obsoleting / hiding legacy variables that are made redundant / obsolete by the unhidden variables.
EDDI Version
4.0.3