Leonard

I'm on the fence about one of the potential features I mentioned, that being custom types for commonly used HTML/CSS types. I think this would be a **very** nice feature,...

> I really dislike the idea of using the component macro for all the components, last time I tried it looked very verbose for large components such as ScrollView Really?...

Oh it also suppresses the `non_snake_case` warning, which is everywhere.

Depends on https://github.com/DioxusLabs/dioxus/pull/2289 because Freya uses the struct pattern syntax (`fn Foo(FooProps { bar }: FooProps)`) which is not supported right now

@xFrednet The advantage is that people who don't want their code to panic wouldn't need to look for various lints to detect various panicking scenarios. I know about `indexing_slicing`, but...

> Ahh, sorry for the confusion. From the linked PR and tag, I assumed that you suggested adding a new lint. AFAIK, Clippy doesn't have a set policy for adding...

I can't think of anything, but I don't have much experience or knowledge about Rust. I don't quite care if it's a group or not though.

May I suggest generating the section from some sort of metadata like `lint_configuration.md`? I started working on it, and the basic structure is pretty repetitive (3x lint name): ```` #...

> I would like to get this documented without just linking users to the Tauri docs. The Tauri docs are often unclear and since we use a different format it...

> You want to create a set of lints, and a binary that runs those lints on an arbitrary project. Exactly. As I mentioned, the ideal outcome would be a...