Check your setup

Open
#218 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, vscode
Domain
developer-experience, tooling

Research direction

Start with the CYF VS Code extension pack and the repository's Prettier setup described in the issue. Verify that Prettier is the default formatter and that saving an HTML file formats it automatically; completion is confirmed when the setup is working and no additional formatter is used.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 📅 Sprint 1 Module-Structuring-And-Testing-Data Setup Submit:None 🦔 Size Tiny
Link to the coursework

CYF VS Code extension pack

Why are we doing this?

You must have the CYF VS Code extension pack installed and Prettier enabled. Don't use another formatter.

🧹 Formatting with Prettier

Using a shared formatting convention makes sure your "diffs" ( differences between the codebase and your changes) only show the code you intentionally wrote, and not a bunch of spaces or tabs. It will also help you read your own code as you work on it.

  1. In Visual Studio open the settings file (Code > Preferences > Settings)
  2. Search for editor format
  3. Set and to
  4. Set the "Default Formatter" to be Prettier
  5. In your editor, write some html and save the file. It should be formatted (indented) automatically.
Maximum time in hours

.15

How to get help

Ask for help on Slack if you are having trouble with Prettier. We will work together on the same files in some workshops, so if you don't have this set up, you will be blocked and unable to participate.

How to submit

It will be entirely obvious if you don't do this. 😜 We can all see!

Dominant language
JavaScript
Stars
0
Forks
397
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Structuring-and-Testing-Data

All issues in CodeYourFuture/Module-Structuring-and-Testing-Data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.