code-annotation
code-annotation copied to clipboard
src-d
🐈 Code Annotation Tool
Currently, we have ~10k features for 1 file pair. Even rendering of such amount of information is slow. We should consider adding pagination or some other UX improvement.
I got the chance to play with the staged application and I have some feedback to give mostly on the UI/UX of the application. ## Landing page This should be...
With the current code each file pair belongs to one experiment. In the future we may want to change this so that a file pair belongs to more than one...
As described by https://github.com/src-d/code-annotation/pull/53#discussion_r165371511 we could reconsider simplifying our color palette. When I reviewed the PR #53 we had 18 different colors. Here are the colors I found in our...
As described by https://github.com/src-d/code-annotation/pull/53#discussion_r165371511 we should use color variables —defined in a `palette.less` stylesheet— instead of hardcoded colors.
I can imagine that after 100 annotation users will feel comfortable with the UI enough for the footer block to become information overload. What I propose is that we have...
context: https://github.com/src-d/code-annotation/pull/49#discussion_r164770518 When an error is returned by a `handler.RequestProcessFunc`, the original error should be logged in the `STDERR`
From @dpordomingo and @mcuadros comments: - [ ] explain better the features provided by our CLU and GUI [#29 (comment)](https://github.com/src-d/code-annotation/pull/29#discussion_r166553539), - [x] assume no context/background in the people reading the...
We use the GitHub username to associate a GitHub account with our internal users, but the username [can be changed](https://help.github.com/articles/changing-your-github-username/). The GitHub user ID should be used instead.