Open Bug 1809478 Opened 2 years ago Updated 2 years ago

Investigate fixing the formatting in messaging-system/schemas/

Categories

(Firefox :: Messaging System, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: aminomancer, Unassigned)

References

(Blocks 1 open bug)

Details

When contributors work on files like this schema or this doc, it's possible their editor setup automatically fixes formatting issues in these files. Ideally, we should disable "format on save" in our editor, and try to use a setup that reads the eslint/prettier config in m-c, or better yet loads the binaries in m-c/node_modules. But I think at least with vscode, that works for js+ files but not much else. So with these json, markdown, etc. files, it seems to default to user's global configuration. And if you're using prettier-eslint for example, it will make some pretty sophisticated fixes, like formatting embedded languages in markdown code blocks. It would be good to get our formatting straight on these files so that either 1) editors/extensions know what to do/what not to do with them, or 2) they are already auto-fixed/formatted the same way prettier-eslint wants to do them.

Blocks: fxms-build
Depends on: 1563927

This is a P3 (P4 maybe) awaiting some updates to the ESLint/Prettier config on m-c, so for now it's just an email reminder when those updates happen. We shouldn't change anything in the meantime since we're not sure what the markdown rules will end up being when it is implemented.

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.