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.

Sign up for GitHub

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

Jump to bottom

field name inconsistency for FullEvent. #2868

Open
jamesbt365 opened this issue May 21, 2024 · 0 comments
Open

field name inconsistency for FullEvent. #2868

jamesbt365 opened this issue May 21, 2024 · 0 comments
Labels
model Related to the `model` module. opinions wanted Discussion or solution to a problem requested.

Comments

@jamesbt365
Copy link
Member

jamesbt365 commented May 21, 2024 •
edited
Loading

When referring to old data we have old, old_if_available, old_data_if_available, old_data and possibly more.

We should improve consistency as these optional fields are only ever there if available.

The new data's field names are also inconsistent in some places too, rectifying this for the next major release would be ideal.
@GnomedDev GnomedDev added opinions wanted Discussion or solution to a problem requested. model Related to the `model` module. labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
model Related to the `model` module. opinions wanted Discussion or solution to a problem requested.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jamesbt365 @GnomedDev