l3ops

Regarding the integration of Suspense, we've been experimenting ways of using Relay through hooks at my company for about 6 months now, and the API we ended up with has...

@sibelius Not yet, though I don't think it would take me much time to publish a fork

This is an issue with the documentation generator, it doesn't implement code generation for all markdown elements yet so these currently fall into a catch-all branch that panics: https://github.com/rome/tools/blob/175cbb7ca6639f6b3d8af09dfa8a13afff392879/xtask/lintdoc/src/main.rs#L248-L251

The parser and formatter crates are left purposefully unaware of each other (so they can be compiled in parallel), so such an entry point would be `rome_js_formatter::format(options, &rome_js_parser::parse(source_code, 0, source_type).syntax())`

> A few suggestions: > > 1. Would you mind adding some valid cases in our generated markdown? https://github.com/rome/tools/pull/3078/files#diff-fdf4fb740794b3a765f8604dee5b3939df2fa9a5bf566e910c31b7db591373bcR26-R31 We can also pull the valid cases from the original rule...

It's not directly related to the formatter, at least until we decide to rewrite literals. This is more of a general purpose, nice-to-have utility but is obviously very low priority...

There are a few things to unpack here: - First the code actions being emitted here are marked as "Suggested fix" and not "Safe fix", this is something we need...

> @leops could you advice about what we should do with this issue? From what I mentioned in my previous comment, I think the general longstanding issue we've had with...

@ematipico It has to do with how the conditional expressions are nested into each other: if you looks closely at the tokens used at the start of each branch you'll...

First of all I should note that symlink are not currently supported to avoid having to track for loops (since that would hinder the performances of directory traversals), but I...