Prettier not respecting `prettier-ignore-start` and `prettier-ignore-end`

Prettier 1.15.2 Playground link

--parser markdown
--prose-wrap never

Input:

- **Sequence of initialization**:
<!-- prettier-ignore-start -->
  #. Firmware
  #. Bootloader (GNU Grub)
  #. Operating System Kernel
  #. Service Manager (e.g. `systemd`)
<!-- prettier-ignore-end -->

Output:

- **Sequence of initialization**:
  <!-- prettier-ignore-start -->
  #. Firmware #. Bootloader (GNU Grub) #. Operating System Kernel #. Service Manager (e.g. `systemd`)
  <!-- prettier-ignore-end -->

Expected behavior: See Input

[jimmyhoran]

I think @anishmittal2020 is onto a great suggestion here. Allowing an explicit range ignore anywhere in any prettier supported file would be very helpful. This kind of implementation is present in many other platform linters and formatters. If you try this out in a prettier playground the range ignore is being ignored 🙈

<!-- prettier-ignore-start -->
<div  class="dark-background">
  </div>
<div class='light-background'></div>
<a href=""/>
<!-- prettier-ignore-end -->

As mentioned above inserting <-- prettier-ignore --> multiple times is not a very nice implementation. A common example would be partials in a HTML file where I would need to do the following…

<!-- prettier-ignore -->
{{ define "title" }}
<!-- prettier-ignore -->
{{ .Title }} &ndash; {{ .Site.Title }}
<!-- prettier-ignore -->
{{ end }}
<!-- prettier-ignore -->
{{ define "main" }}
<!-- prettier-ignore -->
{{ .Content }}
<!-- prettier-ignore -->
{{ end }}

<!-- The rest of my HTML I would like to be formatted -->

Would be much cleaner to be able to do the this…

<!-- prettier-ignore-start -->
{{ define "title" }}
{{ .Title }} &ndash; {{ .Site.Title }}
{{ end }}
{{ define "main" }}
{{ .Content }}
{{ end }}
<!-- prettier-ignore-end -->

<!-- The rest of my HTML I would like to be formatted -->

Is this being worked on by anyone?

[lamyergeier]

Yes, if we could do prettier ignore for a range at any place in the document, it will be great. I think many people would like that, as I think many people might use other standard (like pandoc) for certain things rarely, but mostly they follow commonmark.

I understand from @duailibe comment that Prettier want’s to enforce standard and weed out nonstandard things. IMHO: In the case of source code, people use prettier to standardize code that can be shared. But in the case of markdown usually, people share the generated HTML or PDF and not markdown. So, I think that this feature can be extended to markdown and limited only to Markdown and not to other language like Javascript etc. If people could use some non-standard markdown, it should be ok as they don’t share the source or the markdown file itself.

Also, sensible people won’t misuse prettier-ignore as they would use it rarely because using this at all the places is as good as not using prettier at all.