Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate events to determine whether additional object data can be exposed #2580

Open
2 tasks
Tkael opened this issue Sep 4, 2023 · 0 comments
Open
2 tasks
Assignees
Labels
8. annoyance The behaviour is as specified, but has been found to be annoying in practice by real-world users.

Comments

@Tkael
Copy link
Member

Tkael commented Sep 4, 2023

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

@Tkael Tkael added the 8. annoyance The behaviour is as specified, but has been found to be annoying in practice by real-world users. label Sep 4, 2023
@Tkael Tkael self-assigned this Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8. annoyance The behaviour is as specified, but has been found to be annoying in practice by real-world users.
Projects
None yet
Development

No branches or pull requests

1 participant