The Wayback Machine - https://web.archive.org/web/20200528064039/https://github.com/topics/formatter
Skip to content
#

formatter

Here are 836 public repositories matching this topic...

prettier
JStyle21
JStyle21 commented Apr 20, 2020

Hi,

I'm looking for something like .prettierignore but on a global level, i don't want to copy that file to every new directory i make just to ignore 1 file extension which isn't supported anyway.

AFAIK this isn't supported right?

BTW the extension in this case is EJS which prettier thinks is JS and some other stuff so the best way really is to ignore .ejs as a whole.

black
jason-glassbrook
jason-glassbrook commented Apr 20, 2020

I found that yapf doesn't recognize the SPACES_AROUND_SUBSCRIPT_COLON knob that's listed in the docs. Here's how I produced the error:

Config (setup.cfg)

[yapf]
based_on_style = pep8
spaces_around_subscript_colon = true

Shell

>> yapf -i <filepath>
yapf: Unknown style option "SPACES_AROUND_SUBSCRIPT_COLON"
ntotten
ntotten commented Dec 14, 2019

Currently, when formatters are registered, they are registered for the entire project. This can cause some problems. For example, in the following structure:

/folder1
   package.json
   foo.php
/folder2
   bar.php

If the package.json in folder1 registers the php plugin, then the php plugin will be registered for the whole project. However, when the user opens bar.php the

calebcartwright
calebcartwright commented Apr 10, 2020

rustfmt 1.x ran in "recursive" mode by default wherein all the mods within the AST would be visited and formatted, including those mods defined in external files not explicitly passed as args to rustfmt.

rustfmt 2.x inverts that behavior and will now only format files explicitly passed to rustfmt unless the --recursive flag is passed (in which case rustfmt 2.x formats everything like rus

ribrdb
ribrdb commented Jan 8, 2020

@alexeagle mentioned that the TS style guide has lots of documentation, but it doesn't seem like any of that is available here.
The most common issue we run into is type coercion. Apparently this is what the docs for that should say:
TypeScript code may use the String() and Boolean() (note: no new!) functions, string template literals, or !! to coerce types.

const bool = Boole
malaire
malaire commented Apr 29, 2020

Version: 0.8.2

elm-format changes code (A) into (B) and then when run again (B) into (C).

There are at least two bugs here:

  1. elm-format generates output (B) which it doesn't accept as valid
  2. elm-format mangles two consecutive lists by first moving them closer and then mangling them by separating each list item into its own list.

(A)

{-|

  - one
  - two
  - three
poslegm
poslegm commented Oct 11, 2019

I was a witness and participant of scalafmt adoption into a few large codebases and it always caused the developers to study the scalafmt sources for optimal configuration selection. In my opinion software should not force users to read source code (even if users is programmers).

In my sweet dreams configuration page in docs contains exa

Improve this page

Add a description, image, and links to the formatter topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the formatter topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.