We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
FullEvent
When referring to old data we have old, old_if_available, old_data_if_available, old_data and possibly more.
old
old_if_available
old_data_if_available
old_data
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.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: