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

Incorrect use of the word "dependency" in course prerequisite tree #543

Open
laggycomputer opened this issue Dec 24, 2024 · 1 comment
Open

Comments

@laggycomputer
Copy link
Member

In package resolution parlance, package A is said to be a dependency of package B if package A is required to install package B. This is also true in general usage.

As applied to courses we might say a course taken earlier (say ICS 31) is a dependency of a course taken later (say ICS 32). The converse relation is "dependent"; ICS 32 is a dependent of ICS 31. The relationship between "dependent" and "dependency" is a swap of the subject and object. When dealing with courses in particular, the word "prerequisite" is often used in place of "dependency"; ICS 31 is a prerequisite of ICS 32.

Screenshot_20241224_132449

PeterPortal (and, as a result, AntAlmanac) uses "dependency" when it means "dependent". Particularly in the prerequisite tree, suppose we are focusing on course ICS 32. Then the single prerequisite, ICS 31, is shown to the right. Then one might expect the courses to the left, which require ICS 32, to be referred to as "dependents", but they are instead called "dependencies".

This incorrect naming is also present in Anteater API, meaning any change would be frontend-only. But it is still worth considering.

If consensus is reached agreeing on change, I am willing to see through implementing it.

@Awesome-E
Copy link
Member

Is there a specific instance either in the UI or in the code where it references this as a "dependency" when it's "dependent"? Your screenshot reads how I'd expect it to, i.e. "ICS 33 needs ICS32 [which needs] all of ICS 31"

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

No branches or pull requests

2 participants