Update Prettier & EditorConfig files

[uncenter]

Closes #1610.

[uncenter]

I won't format the files in this PR to avoid conflicts, but we should run the command at some point...

[Snapstromegon]

Hi,
I'm all pro adding a formatter. Did you try running this and see if it has problems with the autogenerated files?
Also do you know whether or not this is run on any git hooks (this might lead to issues until all files in the repo are formatted)?

[uncenter]

Also do you know whether or not this is run on any git hooks (this might lead to issues until all files in the repo are formatted)?

I don't really understand or use Git hooks but it looks to be the case:

  "lint-staged": {
    "*.{js,css,md}": [
      "prettier --write",
      "git add"
    ]
  },

I chose to avoid formatting it here because a) the diff is huge, +-30k lines, and b) I don't want to block other PRs.

Did you try running this and see if it has problems with the autogenerated files?

What do you mean by autogenerated files? If there are any we can just add them to a .prettierignore. There are some files that Prettier struggles with, quite understandably though:

That seems like an interesting approach to whatever that is!

[Snapstromegon]

What do you mean by autogenerated files?

The files in https://github.com/11ty/11ty-website/tree/main/src/_data/community are generated by a GH action from the "Build With 11ty" issues.

[uncenter]

Ah, strange. Well, we can just run the format command after that step in the workflow.

[uncenter]

...where is that workflow?

[uncenter]

I think you are confusing this repo with https://github.com/11ty/11ty-community/tree/main/built-with-eleventy maybe?

[Snapstromegon]

I think you are confusing this repo with https://github.com/11ty/11ty-community/tree/main/built-with-eleventy maybe?

Ah yes, my mistake

[uncenter]

Is there anything else I need to do for this PR? I've ignored that one directory I mentioned that Prettier didn't like, so the command passes now.

[Snapstromegon]

LGTM, but since this is a fairly fundamental change how this repo is worked on, I'd like the opinion of @zachleat on this.

[uncenter]

FYI, the formatting config files (.prettierrc.json, .editorconfig) that I've included here are directly copied from the core @11ty/eleventy repository. So there isn't anything Zach hasn't already approved, technically.

[Snapstromegon]

I think that these configs have to be seen in the context of a project/repo. E.g. editorconfig settings can vary depending on the project. I do not expect Zach to oppose this change, but it makes me more comfortable to have his approval for now.

[uncenter]

@zachleat would you be able to take a look at this? Have some small & incremental improvements in mind for the docs that I'd love to test out but I'd like to have uniform formatting to make for minimal diffs if possible.

[uncenter]

FYI - I've just gone through and compared each of the modified/related files to formatting in this branch and the main branch of the 11ty/eleventy repo and they are (still) consistent.

[uncenter]

@zachleat any chance we could take a look at these changes and then format the repository files once merged?

[zachleat]

Ah, sorry yeah! I’m okay with it as long as it doesn’t mess up any spaces in YAML front matter!

We should add an entry to .git-blame-ignore-revs after this gets applied too

[zachleat]

Rather: I will merge if you can confirm it doesn’t impact YAML front matter whitespace! (and add the entry to .git-blame-ignore-revs)

[uncenter]

Rather: I will merge if you can confirm it doesn’t impact YAML front matter whitespace!

It doesn't appear to.

(and add the entry to .git-blame-ignore-revs)

I think it'd be best for you to commit it on your end instead of making this pull request diff unreadable, and I won't know the commit SHA to ignore until then.

---

I should note that Prettier is running into issues with your use of {% set codeContent %}. It can't tell that this is meant to be code and removes the indentation. Can we use a more idiomatic approach such as regular Markdown code blocks with a post-processing plugin through markdown-it or something?