-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
[api-minor] Implement quadpoints for annotations in the core layer #11013
[api-minor] Implement quadpoints for annotations in the core layer #11013
Conversation
e599b60
to
9114004
Compare
/botio test |
From: Bot.io (Linux m4)ReceivedCommand cmd_test from @timvandermeij received. Current queue size: 0 Live output at: http://54.67.70.0:8877/aefb0172dba4a93/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_test from @timvandermeij received. Current queue size: 1 Live output at: http://54.215.176.217:8877/b827e377091d068/output.txt |
From: Bot.io (Linux m4)FailedFull output at http://54.67.70.0:8877/aefb0172dba4a93/output.txt Total script time: 17.38 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.215.176.217:8877/b827e377091d068/output.txt Total script time: 25.82 mins
|
@Snuffleupagus Do you perhaps have time to review this? |
Sure, I'll try to take a look during the weekend. |
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.
Looks good to me (although I've not looked very closely at the spec).
This commit introduces the required core layer support for #6811. In a next commit, we can introduce the display layer support for this feature.
Note that four annotation types that didn't have unit tests before (because they practically didn't have any logic) now have unit tests, which is also an improvement for our unit test coverage.