schultyy / cabinet Goto Github PK

If a user is part of multiple organisations, it makes sense to add repositories from these as well.

The README should explain the following:

• What this project is about
• Requirements
• Technologies

It should be possible to leave a comment on an issue. Additionally also close / open it by leaving the comment.

It should be possible to create a new issue in a repository

It should be possible to mark repositories as favorite to build up a list of commonly used repos which then also show up on top of the repo list.

The repository list should tell the user which repositories are public and which are private.

• I open a repository
• I click "New Issue"
• Then I switch the repository
• I expect that I'll see the issue list for that new repository

I'm getting the following error on one of my Private Repos.

ApolloError.js:32 Uncaught (in promise) Error: GraphQL error: Could not resolve to a Repository with the name 'fraserbooth/OptBP-Core'.
at new t (ApolloError.js:32:1)
at QueryManager.js:266:1
at QueryManager.js:701:1
at Array.forEach ()
at QueryManager.js:698:1
at Array.forEach ()
at e.broadcastQueries (QueryManager.js:695:1)
at Array. (QueryManager.js:65:1)
at f (createStore.js:173:1)
at ApolloClient.js:174:1

...another smaller Repo with the same security settings is working fine.

Interestingly both Repo's are actually under OptimiseHealth rather than fraserbooth. I wonder why one is looking in the correct place an the other not, despite both appearing in a similar structure in the Repo list.

Has anyone else experienced this?

Any ideas how to resolve the problem?

Thanks :)

The repository list should provide the information for which repository we already have issues downloaded.

To improve render performance we should consider moving everything over to Immutable.js objects.

It should be possible to hide closed issues

On the create token screen the reload repositories button is visible although it should be hidden

When the user is online it'd be handy if the repositories and issues could update itself.

We should render the the following data for an issue as well:

• labels
• assignee
• creator
• Avatar image(s)
• Milestone
• Comments

As a user I want to be able to edit an issue's milestone and assignees. This should be possible for both new and already existing issues.

The ordering of the Repository list shouldn't be random but either by repository created date or last active (like on GitHub).

Follow up for #19

Queue ordering: An issue has to be created first, then it can marked as resolved

Consider the following scenario:

• A user is offline
• They create a new issue
• They mark the issue as solved
• They get back online

The problem here is the following:

• The queue must be ordered: First create issues, then change their statuses
• When an issue got created we need to back-fill the issue's number into all subsequent tasks belonging to it (like changing the state)

If a selected repository doesn't have issues render a text which says "This repository doesn't have any issues"

If we already fetched issues for a certain repository it should be possible to refetch them

Sometimes it can happen that an issue's body content is wider than expected. This results in horizontal scrolling. It would be nice to instead restrict the content width and let the words wrap into the next line.

If a user redownloads issues it should be possible to distinguish between already seen and new issues. The ones which are new should have a visual indicator.