Add Grades feature

[Justin-Fernbaugh]

Pull Request Template

Screenshots

Description

I've added a Grades table that populates or updates the grades of a user after they respond to a question(Responses.js). Moreover, these changes involve using points that are added to questions using the 'weights' attribute of a question. The 'weights' of a question can be added or if they're not present will be auto-populated with a default value of '1' for each.

Important: before testing this branch the databases have to be dropped, re-added, and then migrated/seeded. The first four steps must be performed in MySQL while steps 5-8 are performed in the dir server/

1. DROP DATABASE myclassroom_development;
2. CREATE DATABASE myclassroom_development;
3. DROP DATABASE myclassroom_test;
4. CREATE DATABASE myclassroom_test;
5. npx sequelize-cli db:migrate --env test
6. npx sequelize-cli db:migrate --env dev
7. npx sequelize-cli db:seed:all --env test
8. npx sequelize-cli db:seed:all --env dev

Fixes # (issue)

Additional Information

Checklist:

Before you submit your Pull Request, please make sure you have completed the following tasks:

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.
• I have tagged my PR with the appropriate label(s).

[nilsstreedain]

Looks like this PR has the same issue that @Durbin-Elijah's did. If you remember, awhile back, we had an unknown contributor who made a PR to main that got accepted, causing divergent history between main/dev because all changes on main were intended to come directly from dev, nowhere else. It appears the branch submitted in this PR was pulled from main instead of dev causing it to try to merge those non-existent commits to dev. Would it be possible to go through and remove any commits that are not apart of this change so once we are ready for a new version, I can force override main? (Only force overriding because our branches should be built from dev, not main.)

[Justin-Fernbaugh]

Looks like this PR has the same issue that @Durbin-Elijah's did. If you remember, awhile back, we had an unknown contributor who made a PR to main that got accepted, causing divergent history between main/dev because all changes on main were intended to come directly from dev, nowhere else. It appears the branch submitted in this PR was pulled from main instead of dev causing it to try to merge those non-existent commits to dev. Would it be possible to go through and remove any commits that are not apart of this change so once we are ready for a new version, I can force override main? (Only force overriding because our branches should be built from dev, not main.)

Yeah, I should be able to do this, would you be able to point me to which commit this starts so I can remove the changes?

[nilsstreedain]

Yeah, I should be able to do this, would you be able to point me to which commit this starts so I can remove the changes?

Looks like just commits c6524de, 86d4753, and 5ed0d93 need to be removed, preferably with a rebase. If anything is left committing to /client, that should also probably be removed.

[Justin-Fernbaugh]

Merged with changes from dev and dropped any changes from main. Ready for a second look

[nilsstreedain]

Generally looks great, see comments for 2 minor changes I found.

[nilsstreedain]

Looks great!

[nilsstreedain]

Looks great, nice job!