fix: broken skip link in Learner Dashboard

[Ankush1oo8]

Fixed issue #510
Learner Dashboard has a broken skip link

[openedx-webhooks]

Thanks for the pull request, @Ankush1oo8!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @2U-aperture. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[jsnwesson]

This is looking much better, @Ankush1oo8 ! I did notice that one test that is failing is a lint where they want you to use double quotes instead of single quotes.

[Ankush1oo8]

This is looking much better, @Ankush1oo8 ! I did notice that one test that is failing is a lint where they want you to use double quotes instead of single quotes.

Changing it

[Ankush1oo8]

I have changed the single quotes to double quotes

[jsnwesson]

Great! Now it looks like some of the Snapshot tests need to be updated (according to failing tests).

In your remote branch, you should be able to see what tests are failing by running npm run test.
You'll see some Jest Snapshots failing, because you made a change to the App.

To fix those snapshots, you would run npm run snapshot

[Ankush1oo8]

I tried to run the commands you told its showing fedx scripts not found

[jsnwesson]

@Ankush1oo8 ah, you'll need to first run npm install to install the dependencies, which includes fedx-scripts, then you can run all of the other NPM scripts (ie. npm run lint, npm run test, npm run snapshot).

[Ankush1oo8]

@Ankush1oo8 ah, you'll need to first run npm install to install the dependencies, which includes fedx-scripts, then you can run all of the other NPM scripts (ie. npm run lint, npm run test, npm run snapshot).

I have installed all dependencies prior to running the commands

[jsnwesson]

@Ankush1oo8 that's weird. I pulled your PR to my local machine, and when I simply run npm run snapshot without doing any install, I see the error you must be getting.

Once I run npm install and then run npm run snapshot, it works perfectly as expected. To confirm, what command did you run to install the dependencies? And do you see a folder node_modules at the top of the Learner Dashboard directory? That would confirm that you installed the dependencies successfully, and fedx-scripts would be in there.

[Ankush1oo8]

First i have done npm install then other cmds

[jsnwesson]

@Ankush1oo8 and can you confirm that you see a folder node_modules at the top of the Learner Dashboard directory?

[Ankush1oo8]

@jsnwesson yes node modules folder is present

[jsnwesson]

Hey @Ankush1oo8 , hope you're well! I'm not sure what the problem could be for you, but I'd encourage you to look through the Open edX developer documentation to see if someone has found a similar problem and solution for it, or to look through the Open edX Slack space.

[itsjeyd]

@Ankush1oo8 Thank you for this contribution!

Just wanted to highlight that you'll need to submit a signed contributor agreement (CLA) at some point. There's no rush, but we can't merge this PR without that.

You can check this comment from the PR bot for details.

[Ankush1oo8]

@Ankush1oo8 Thank you for this contribution!

Just wanted to highlight that you'll need to submit a signed contributor agreement (CLA) at some point. There's no rush, but we can't merge this PR without that.

You can check this comment from the PR bot for details.

I have filled the form