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

fix(curriculum): enhanced grammer and flexibility in tests to accommodate any valid response #53786

Conversation

aaqib605
Copy link
Contributor

Checklist:

Closes #53700

@github-actions github-actions bot added the scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory. label Feb 18, 2024
@gikf
Copy link
Member

gikf commented Feb 18, 2024

Hey @aaqib605

Thank you for opening this pull request and being eager to contribute.

You have already another PR, which will be merged, for issue limited to the "first time" code contributors to this repository. Let's leave this issue one for other first timers. Because of that I'm going to close this PR. We would welcome future pull requests from you.

Thank you and happy coding.

@gikf gikf closed this Feb 18, 2024
@aaqib605
Copy link
Contributor Author

Hey @aaqib605

Thank you for opening this pull request and being eager to contribute.

You have already another PR, which will be merged, for issue limited to the "first time" code contributors to this repository. Let's leave this issue one for other first timers. Because of that I'm going to close this PR. We would welcome future pull requests from you.

Thank you and happy coding.

@gikf I appreciate your consideration and I look forward to contributing in the future.

Thank you again and have a great day!

@aaqib605 aaqib605 deleted the fix/grammar-issues-and-update-tests-in-step-29-of-music-player-project branch February 19, 2024 06:15
@srikanth-kandi
Copy link
Contributor

@gikf, I think this is not for first time contributors

Please recheck the issue #53700

@aaqib605 aaqib605 restored the fix/grammar-issues-and-update-tests-in-step-29-of-music-player-project branch February 19, 2024 13:50
@gikf
Copy link
Member

gikf commented Feb 19, 2024

Hmm, welp 🤦‍♂️ . You are right @srikanth-kandi, thanks!

@aaqib605 my apologies.

@gikf gikf reopened this Feb 19, 2024
@gikf gikf added status: waiting review To be applied to PR's that are ready for QA, especially when additional review is pending. new javascript course These are for issues dealing with the new JS curriculum labels Feb 19, 2024
@aaqib605
Copy link
Contributor Author

@gikf Never mind. Happens to the best of us. Happy to contribute.

Copy link
Member

@Ksound22 Ksound22 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The second test only passes if the condition is userData?.currentSong === null || userData?.currentSong.id !== song.id.

Can you try and look into that too?

@aaqib605
Copy link
Contributor Author

The second test only passes if the condition is userData?.currentSong === null || userData?.currentSong.id !== song.id.

Can you try and look into that too?

@Ksound22 Done. Now the tests work for all possible code variations.

@aaqib605 aaqib605 force-pushed the fix/grammar-issues-and-update-tests-in-step-29-of-music-player-project branch from c97393a to 8c5295f Compare February 21, 2024 05:51
@Ksound22
Copy link
Member

Ksound22 commented Feb 21, 2024

The second test only passes if the condition is userData?.currentSong === null || userData?.currentSong.id !== song.id.
Can you try and look into that too?

@Ksound22 Done. Now the tests work for all possible code variations.

No. The second test is not reached anymore for the three possible conditions from the issue
Screenshot 2024-02-21 at 8 24 52 AM

@aaqib605
Copy link
Contributor Author

aaqib605 commented Feb 21, 2024

@Ksound22 Made the necessary changes. It should work fine now.

Screenshot 2024-02-21 at 1 49 14 PM Screenshot 2024-02-21 at 1 49 35 PM Screenshot 2024-02-21 at 1 50 01 PM

Hey @aaqib605 👋🏽

The second test is only reached when the condition is exactly userData?.currentSong.id !== song.id || userData?.currentSong === undefined.

I'm looking into what I can do on my end.

@gikf
Copy link
Member

gikf commented Mar 11, 2024

@aaqib605 Unfortunately I'm not seeing any new commits on the PR branch: https://github.com/freeCodeCamp/freeCodeCamp/pull/53786/commits

Please make sure they are pushed to the right branch. Join us in our chat room or the forum if you need help with it, our moderators will guide you through this.

@gikf gikf removed the status: merge conflict To be applied to PR's that have a merge conflict and need updating label Mar 11, 2024
@aaqib605
Copy link
Contributor Author

the forum

@gikf I have asked for help on discord.

However i want to know that my PR branch and my forked repositories' main branche are aligned, and the code is functioning as expected. What might be causing the delay in merging the pull request?

@ilenia-magoni
Copy link
Contributor

What might be causing the delay in merging the pull request?

the pull request is not ready to be merged, you need to make changes to the branch to make the tests work correctly

@aaqib605
Copy link
Contributor Author

Could you please take a look at the freeCodeCamp discord forum, asked for help there
https://discord.com/channels/692816967895220344/1019641182340534294/threads/1217091995600683139

@aaqib605
Copy link
Contributor Author

Should i just make a new PR?

@Ksound22
Copy link
Member

Should i just make a new PR?

I think you should.

@aaqib605 aaqib605 force-pushed the fix/grammar-issues-and-update-tests-in-step-29-of-music-player-project branch from 2710112 to b5a53a2 Compare March 22, 2024 11:47
@ilenia-magoni
Copy link
Contributor

Now it works as requested! Sorry for the noise

I have a little point to make:
image
So userData?.currentSong === undefined should not actually pass

@Ksound22
Copy link
Member

Ksound22 commented Apr 4, 2024

Hey @ilenia-magoni 👋🏽

Thanks for requesting I review this again. It's now okay with me. Could you please take a look at it yourself and approve it?

This took a lot of time, so I think it needs an extra eye.

Copy link
Member

@Ksound22 Ksound22 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for not giving up on this, @aaqib605!

Copy link
Contributor

@ilenia-magoni ilenia-magoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now it works as requested! Sorry for the noise

I have a little point to make:
undefined === null is false
So userData?.currentSong === undefined should not actually pass

@aaqib605
Copy link
Contributor Author

aaqib605 commented Apr 5, 2024

Thanks for not giving up on this, @aaqib605!

I would like to thank everybody for their support.

@aaqib605
Copy link
Contributor Author

aaqib605 commented Apr 5, 2024

Now it works as requested! Sorry for the noise

I have a little point to make: undefined === null is false So userData?.currentSong === undefined should not actually pass

@ilenia-magoni Could you please explain this in more detail, like how it affects the solution?

@ilenia-magoni
Copy link
Contributor

ilenia-magoni commented Apr 5, 2024

Now it works as requested! Sorry for the noise
I have a little point to make: undefined === null is false So userData?.currentSong === undefined should not actually pass

@ilenia-magoni Could you please explain this in more detail, like how it affects the solution?

The condition for the if statement is to check if userData?.currentSong is null, checking if it is undefined doesn't complete this goal, because if it is null, null === undefined is still false, so you should remove userData?.currentSong === undefined from the accepted solutions. You allow it with this part of the regex userData\?\.currentSong\s*===\s*undefined. That would be removing that section from two places in each test.

@jdwilkin4
Copy link
Contributor

jdwilkin4 commented Apr 15, 2024

HI @aaqib605 !

It looks like there is one last change requested for this PR left in this comment here
#53786 (comment)

It could make that change, then we should be good to go with this PR 👍

@aaqib605
Copy link
Contributor Author

HI @aaqib605 !

It looks like there is one last change requested for this PR left in this comment here #53786 (comment)

It could make that change, then we should be good to go with this PR 👍

Thanks, everybody for the patience, I am working to implement this little change.

Copy link
Contributor

@ilenia-magoni ilenia-magoni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be the solution for my last review

@ilenia-magoni ilenia-magoni self-requested a review May 6, 2024 17:00
@camperbot
Copy link
Contributor

This PR seems to make similar changes as an existing PR. As such, we are going to close this as a duplicate.

If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.

Thanks again! 😊


If you have any questions, feel free to ask questions on the "Contributors" category on our forum or the contributors chat room.

@camperbot camperbot closed this May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new javascript course These are for issues dealing with the new JS curriculum scope: curriculum Lessons, Challenges, Projects and other Curricular Content in curriculum directory. status: waiting update To be applied to PR if a maintainer/reviewer has left a feedback and follow up is needed from OP
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix grammar issues and update tests in step 38 of music player project
9 participants