First pass at tables for sharing logs with the teams #17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This introduces the concept of a Session, which may or not map exactly to an actual session of matches, that a given collection of archives is used for. Running a Session then generates various Artefacts which we want to share with the teams (logs, animations, possibly other things). We assume that for some types of Artefact, teams should only able to view those which relate to their robot. With thanks to James for design discussion. Co-Authored-By: James Seden Smith <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces the concept of a Session, which may or not map exactly to an actual session of matches, that a given collection of archives is used for. Running a Session then generates various Artefacts which we want to share with the teams (logs, animations, possibly other things). We assume that for some types of Artefact, teams should only able to view those which relate to their robot.
With thanks to @sedders123 for design discussion.