Skip to content

Salem Ba-rabuod - #11

Open
Barboud wants to merge 1 commit into
HackYourAssignment:mainfrom
Barboud:main
Open

Barboud wants to merge 1 commit into
HackYourAssignment:mainfrom
Barboud:main

Conversation

@Barboud

@Barboud Barboud commented Apr 1, 2026

Copy link
Copy Markdown

No description provided.

@github-actions

github-actions Bot commented Apr 1, 2026

Copy link
Copy Markdown

📝 HackYourFuture auto grade

Assignment Score: 0 / 100 ✅

Status: ✅ Passed
Minimum score to pass: 0
🧪 The auto grade is experimental and still being improved

Test Details

@mvcatsifma

Copy link
Copy Markdown

@Barboud Taking this review.

@mvcatsifma

mvcatsifma commented Apr 7, 2026 •

Copy link
Copy Markdown

@Barboud

The output matches exactly — well done. The implementation is correct and the storage abstraction works as intended.

A few points to improve:

Commit messages
"solved the assignment" as a single commit covers everything: schema, migration, and all functions. This makes it hard to understand what changed and why. Prefer smaller, incremental commits (e.g. one function or logical step at a time) with descriptive messages.

Tests
There are no tests. In this case manual verification was done correctly, but it’s still fragile. A few simple assertions would make the implementation more robust and prevent regressions.

Assignment scope
app.js was modified (quote style changes). The README explicitly says not to modify this file, so it should be left unchanged.

cc @stasel

@mvcatsifma
mvcatsifma self-requested a review April 9, 2026 06:26
@mvcatsifma mvcatsifma added the Reviewed This assignment has been reivewed by a mentor and a feedback has been provided label Apr 9, 2026
@Barboud

Barboud commented Apr 10, 2026

Copy link
Copy Markdown
Author

@Barboud

The output matches exactly — well done. The implementation is correct and the storage abstraction works as intended.

A few points to improve:

Commit messages "solved the assignment" as a single commit covers everything: schema, migration, and all functions. This makes it hard to understand what changed and why. Prefer smaller, incremental commits (e.g. one function or logical step at a time) with descriptive messages.

Tests There are no tests. In this case manual verification was done correctly, but it’s still fragile. A few simple assertions would make the implementation more robust and prevent regressions.

Assignment scope app.js was modified (quote style changes). The README explicitly says not to modify this file, so it should be left unchanged.

cc @stasel

Thanks @mvcatsifma for the feedback.

I have already applied your advice about commit messages in my latest assignment.
Regarding tests, I'm still a bit confused. Should I write a test unit for every single function, or just the main parts?
I'll also be more careful with the assignment requirements next time. Thanks again!

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

Labels

Reviewed This assignment has been reivewed by a mentor and a feedback has been provided

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants