Giter Club home page Giter Club logo

Comments (3)

slinkydeveloper avatar slinkydeveloper commented on June 11, 2024

My pattern for doing this is to:

  • Annotate fields using the serde default feature support, annoying but it works :)
  • Instantiate the figment with let figment = Figment::from(Serialized::defaults(MyConfig::default())) and later merge with the other config providers

from figment.

SergioBenitez avatar SergioBenitez commented on June 11, 2024

If you don't want to use serde's default attribute, nor create a secondary struct, the simplest option, albeit unsatisfying, is to merge the default values into a Figment manually:

Figment::new()
    .merge(Serialized::default("host", ...))
    .merge(Serialized::default("port", ...))

Extracting your type from this Figment (with the desired providers added) would then only require the required field(s).

You could also apply this idea in reserve by serializing your default struct with all of its field into a figment, setting the required fields to None, and then extracting from there.

Unfortunately I don't know of a better solution in Rust. There is unfortunately no way to say "give me a struct with the same fields as this struct expect exclude these," which is what we'd need here. You could theoretically write a procedural derive to accomplish this, though I'm not aware of a crate that does this, and a quick search turned up empty, but perhaps you'd have more luck.

from figment.

jalaziz avatar jalaziz commented on June 11, 2024

You could also apply this idea in reserve by serializing your default struct with all of its field into a figment, setting the required fields to None, and then extracting from there.

For this approach, do you mean have default that sets all fields (potentially with some dummy values), then use Serialized::default("port", ...) to set the override and set required fields to None?

Unfortunately I don't know of a better solution in Rust.

Yeah, I tried searching myself and it's not an easy thing to search for. I'm also not convinced it would be any cleaner.

I ultimately went with serde's default feature. Even though it means I have to define functions for every default, it's a scalable pattern. I didn't use Serialized::defaults(...) though, since that would require all the fields to be set.

Thanks everyone for the input. Always good to confirm I'm not missing the obvious 😄.

from figment.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.