Can you give me more cases for current behavior and your expected behavior?

For exemple, given these snippets (with the "quote" config to "double"):

<div data-content="{% if status == "active" %}Id like it{% endif %}"></div>

<input
  name="{{ field.name }}"
  id="{{ field.name }}"
  type="{{ field.type }}"
  value="{{ field.value|default("", true) }}"
>

<button class="{{ ["btn_class", "btn-expand"]|join(" '") }}" data-toggle="collapse">

<button
  class="{{ ["btn_class", "btn-expand"]|join(" ") }}"
  data-toggle="collapse"
>
</button>

This get currently reformated as (see playground):

-<div data-content="{% if status == "active" %}Id like it{% endif %}"></div>
+<div data-content='{% if status == "active" %}Id like it{% endif %}'></div>

<input
  name="{{ field.name }}"
  id="{{ field.name }}"
  type="{{ field.type }}"
- value="{{ field.value|default("", true) }}"
+ value='{{ field.value|default("", true) }}'
>

<button
-  class="{{ ["btn_class", "btn-expand"]|join(" ") }}"
+  class='{{ ["btn_class", "btn-expand"]|join(" ") }}'
  data-toggle="collapse"
>
</button>

I would like nothing to happen because this is valid Jinja that will resolve to valid HTML so no need to switch the quote.
That way, the quote style would be respected.

Hey @g-plane , thanks for making this awesome plugin, I'm using it with dprint and biome for a vue project and it's amazing.
However I've encountered a similar issue as @UnknownPlatypus :

Given

<div v-if="snapshot.matches('INIT')" role="group">

dPrint format it as :

<div v-if='snapshot.matches("INIT")' role="group">

I would expect markupt_fmt to always format stuff into the first given style, when using valid html (ie vue) and the quote option is set as double.
For Jinja I'm not sure how to handle that, given that it is invalid html, perhaps a way to allow jinja quote styles ? That seems harder.

This is using "quotes": "double", markup_fmt-v0.13.1, and dprint ^0.47.2.

@Hebilicious I could not reproduce your issue with markup_fmt-v0.18.0 version (See playground)

Consider adding a playground link next time to ease later debugging.

Your use case might have been already fixed by #37