Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[core] Split DUNE structure from their cfg conterpart #8

Open
nrybowski opened this issue Feb 17, 2025 · 0 comments
Open

[core] Split DUNE structure from their cfg conterpart #8

nrybowski opened this issue Feb 17, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@nrybowski
Copy link
Owner

Currently, the main structures of DUNE are defined in cfg.rs and are used to directly decode the configuration from a TOML file.
But they are also used to transfer serialized state to remote phynodes with DUNE's internal data that are not present in the configuration file.
Hence, a lot of fields are wrapped into Options to allow TOML configuration decoding in presence of inner data, which implies more useless boilerplate.

Structures representing DUNE elements (and the associated behaviors) must be separated from their configuration conterpart, and should be moved to lib.rs.

@nrybowski nrybowski added the enhancement New feature or request label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant