Open tigerros opened 10 months ago
Bundler settings are copied from tauri-bundle (more docs here). (The only reason we don't use tauri's structs directly is because tauri's structs don't implement serialize and deserialize which we need to convert them to and from toml)
Bundler settings are copied from tauri-bundle (more docs here)
That explains it. I suppose linking the tauri docs would be sufficient then. Also, does the TUI use the tauri bundler, or only desktop and mobile? For the docsite.
Bundler settings are copied from tauri-bundle (more docs here)
That explains it. I suppose linking the tauri docs would be sufficient then. Also, does the TUI use the tauri bundler, or only desktop and mobile? For the docsite.
I think it should work for TUI, but I haven't tested it. Mobile cannot use dx bundle yet
Specific Demand
There's some values in the
Dioxus.toml
which aren't documented on the website or even the source code itself. I looked in the 0.3.0 book as well, and they don't seem to be there either. It seems strange to me that these would be undocumented, but I guess that's the case.Additionally, it would be great if there was a way to generate an example
Dioxus.toml
that would contain all possible values. This would allow us to replace the dioxuslabs.com configuring page with a link to the docs.rs, thus reducing the amount of documentation we need to maintain.Implement Suggestion
Initially, I wanted to document them myself, but realized it's difficult seeing as I didn't write it, and I only have experience with the web configuration (which is documented). However, I've got some suggestions.
The config structs are in cli/src/config.rs. The documentation for some of them is on the dioxuslabs.com configuring page, so that can be copied. Other documentation needs to be added though.
As for generating the example, we could use something like this:
Output: