-
Notifications
You must be signed in to change notification settings - Fork 60
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
Remove deprecated EventStore based I/O functionality #485
Conversation
fbac5c0
to
ca76f6f
Compare
ca76f6f
to
fc8f9ec
Compare
05fbeee
to
57fc758
Compare
What is left to do here is essentially checking the documentation for remnants of the EventStore but we could also address that in fixing the documentation for version 1.0. |
8ef2475
to
08decf9
Compare
08decf9
to
36ae95f
Compare
Now, I think I got everything EventStore related including documentation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meta data can be stored and retrieved from the `EventStore` for runs, collections and events via | ||
the three methods: | ||
```cpp | ||
virtual GenericParameters& EventStore::getRunMetaData(int runID); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add a small explanation that one just creates a frame if there is a metadata use case? Just to explain a bit more the frame concept
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for a non-default one where putting a parameter is not enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add this in this PR still, or do we push it into the documentation update?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That can go to a separate PR
d5b39ce
to
21ac325
Compare
No longer depend on writing the legacy file in the process
08a85b5
to
0bd2cdb
Compare
Not entirely sure what to make of CI at the moment. Things that fail in CI are working locally, and things that fail locally are failing in CI... |
46ebf51
to
9a53143
Compare
9a53143
to
65fbe65
Compare
BEGINRELEASENOTES
ENDRELEASENOTES
This is currently only the first steps to remove the EventStore based I/O functionality (as outlined in #429). It is quite far from complete. The main purpose at this point is to get a feeling of how many things need to be touched in the end.This removes all traces of theEventStore
and related readers and writers.