Tailwind supports automatic class sorting with Prettier. It would be nice if this formatter could somehow incorporate that functionality. Perhaps it could be an optional feature, that if enabled, would check if a class attribute was a string literal, and if so, it would sort the class names in that string similarly to how prettier-plugin-tailwindcss does it.

The formatter currently removes comments. It would be nice to have the option to preserve comments (or perhaps this could be made the default behavior).

attr_value_brace_style

Whether or not to add braces around single expression attribute values.

• Default value: "WhenRequired"
• Possible values: "Always", "AlwaysUnlessLit", "WhenRequired", "Preserve"

Examples

"AlwaysUnlessLiteral":

<div on:click=move |_| set_value(0) disabled=is_disabled />
<img width=100 height={200} class="banner" alt={"test"} />

// BECOMES

<div on:click={move |_| set_value(0)} disabled={is_disabled} />
<img width=100 height=200 class="banner" alt="test" />

"Always":

<div on:click=move |_| set_value(0) disabled=is_disabled />
<img width=100 height={200} class="banner" alt={"test"}>

// BECOMES

<div on:click={move |_| set_value(0)} disabled={is_disabled} />
<img width={100} height={200} class={"banner"} alt={"test"} />

"WhenRequired": (default)

<div on:click={move |_| set_value(0)} disabled={is_disabled} />
<img width=100 height={200} class="banner" alt={"test"} />

// BECOMES

<div on:click=move |_| set_value(0) disabled=is_disabled />
<img width=100 height=200 class="banner" alt="test" />

"Preserve":

<div on:click=move |_| set_value(0) />                              // stays untouched
<div on:click={move |_| set_value(0)} />                            // stays untouched
<img width=100 height={200} class="banner" src={"./banner.jpg"} />    // stays untouched

It seems as though paragraphs that wrap and are indented are repeatedly indented upon re-running LeptosFmt, so they creep further to the right each time.

(This is inside a view! macro):

                <p class="mb-4">
                        "At Houski Inc, we are committed to protecting the privacy of our
                                      users. This privacy policy explains how we collect, use, and share
                                      information when you use our website, property data system, and APIs
                                      (collectively, the \"Services\"). By using our Services, you agree to
                                      the collection, use, and sharing of your information as described in
                                      this privacy policy. If you do not agree with our policies and
                                      practices, do not use our Services."
                    </p>

If this isn't easily reproduced I can supply more code.

Implements https://github.com/bram209/leptosfmt/issues/12

Now, by adding a --check flag, the program will exit unsuccessfully if it should have made changes to the files. If it didn't need to make any changes, then it will exit successfully, as usual.

This main check happens within the source_file::format_file_source function, however similar logic seems to be in source_file::format_expr_source. Do we need to copy this logic into that function as well?

Similar to cargo fmt where if --check is passed, then if anything needs to be formatted, the program exits with a non-zero exit code, indicating that the formatting was not correct.

Resolves #3

Note: Currently inserts the doc comments before a node. Inline (at end of a statement) comments are not yet supported (and will end up in the line above).

Note2: This does not preserve comments in code blocks yet, I plan to add this to https://github.com/bram209/prettyplease later.

the issue is that syn interpreters non-doc comments as white space: https://doc.rust-lang.org/reference/comments.html#non-doc-comments

workaround involves extracting the comments from the source text directly.