You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.
The plan would be to be able to skip "enum" and "type" at least.
One design problem left is : It works well for an enum but typsfmt_lib::Config is a struct with other fields, it should create a "section" with all it's own field inside which might mean we would need a more powerful trait
I recently realized that I want to generate this file programmatically for other reasons (to support syntax highlighting for other languages in fenced code blocks). I'll take a look at this today, and I'll see if I can work in something like this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This would use a trait on each field
we could have a macro to generate an implementation for the trait
impl_T!(typsfmt_lib::Config,"description","type","enum","enum description")
The plan would be to be able to skip "enum" and "type" at least.
One design problem left is : It works well for an enum but
typsfmt_lib::Config
is a struct with other fields, it should create a "section" with all it's own field inside which might mean we would need a more powerful trait#381
The text was updated successfully, but these errors were encountered: