Skip to content
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

Model: Update #96

Closed
CookingWithCale opened this issue Jan 1, 2024 · 0 comments
Closed

Model: Update #96

CookingWithCale opened this issue Jan 1, 2024 · 0 comments
Assignees

Comments

@CookingWithCale
Copy link
Collaborator

CookingWithCale commented Jan 1, 2024

Problem

The problem I am addressing on this mission is that the model is completely bozo.

Solution

The solution that I'm addressing on this mission is to switch to a model where I the root object is the crew, and each crew member has a list of repositories, they have access to their private repos but I do not unless I have been added as a contributor, then those private repos will appear in my list of private repos.

I can't just store all information in the Chrome local storage, and caching data is not really what I want, but I do want to minimize the traffic. I need to store a list of all my repos, and I need to be able to select one repo, then I need to the the open or the closed issues. The issue tickets will change much more frequently than the list of repos, so it makes sense to just store a list of the AccountHandle/RepoName, then when I select a repo then I need to load the issue tickets, but probably not the closed ones at first.

Affected Files

  1. ~/**/*.*

Hierarchy

Tags

Mission

A

Sessions

License

Copyright AStartup; all rights reserved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant