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.

Sign up for GitHub

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

Jump to bottom

Catch "double" coreqs #95

Open
haydenfree opened this issue Jun 5, 2020 · 1 comment
Open

Catch "double" coreqs #95

haydenfree opened this issue Jun 5, 2020 · 1 comment
Assignees
@heileman

Comments

@haydenfree
Copy link
Member

If two courses list each other as a coreq, for the sake of graph traversal, remove one of the relationships from the graph representation to avoid a cycle. Keep the relationship stored on the data side. That is, in the requisites array on each course.
@haydenfree
Copy link
Member Author

If two courses list each other as coreqs then that is really a strict coreq? We should just pick one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@heileman heileman

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@heileman @haydenfree