Code Monkey home page Code Monkey logo

config's People

Contributors

chrisfjones avatar clyfe avatar hlship avatar michalmarczyk avatar nblumoe avatar sktoiva avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

config's Issues

Move towards clojure.spec?

Given that config is still in alpha, the idea of moving towards clojure.spec (in Clojure 1.9) may become compelling.

Pros:

  • No dependencies.
  • Standard model.
  • All the other spec benefits.

Cons:

  • Keys must be namespace qualified keys.
  • YAML support becomes very awkward (again, namespaced keys).
  • Command line support is, again, awkward due to namespaced keys.
  • Really abandons backwards compatibility to earlier alphas.
  • Required Clojure 1.9.

Optional keys and expansions

It's a pretty common case that I want optional config keys because the function that will eventually take in that config has its own fallbacks. For example, with langhor (library for RabbitMQ), the connect function accepts a map of connection parameters, e.g. :host, :port, :username etc., all of which are optional and have defaults if they're not provided. So it makes sense for me to model my config after the map the connect function accepts and exploit the built-in fallbacks. Furthermore, when I do want to set a value, I want to do it with environment variables. However, there doesn't seem to be a way to tell this library to optionally include a key based on whether or not an environment variable expansion is successful. The only way to avoid an exception is to provide a non-nil default, but that would require me to essentially duplicate the defaults that are already handled by langhor. Would it be possible to have some kind of reader conditional for optional configuration within a profile (perhaps where nil as a value drops the key)?

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.