Coder Social home page Coder Social logo

pricing's People

Contributors

bojanz avatar colinodell avatar dwkitchen avatar lsolesen 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 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 avatar avatar avatar avatar avatar avatar avatar

Forkers

joshuataylor mglaman pcambra marquisknox colinodell sorinsarca happysj kemeice shankarthiyagaraajan wesavetheworld cambricorp

pricing's Issues

Rounding functionality

Commit 72cdebe completely removed rounding functionality without adding an alternative. I am therefore unable to perform any rounding with the current version of this library.

Would you consider reverting that commit until the new "Rounder objects" have been implemented?

No tags

Is this library not stable enough for a tag, or is it just that no ones got round to it yet?

Cannot install with commerceguys/intl 0.5

I'm unable to lock my version of commerceguys/intl to 0.5 because it's technically incompatible with the dev-master requirement of this package:

2015-03-11_09-52-29

That behavior sorta makes sense though (in a weird way) since dev-master may contain changes not present in an earlier release.

I'm therefore forced to either:

  1. Require an unstable version of commerceguys/intl; or,
  2. Use an alias to trick Composer into thinking the 0.5 release is dev-master:

2015-03-11_10-00-41

Neither workaround is ideal - the former introduces potentially unstable code into my system, and the latter doesn't seem to allow version constraint ranges like 0.5.*, 0.*, ~0.5, etc.

Would you consider modifying composer.json so that stable packages can be used?

I think ~0.5 would be good if you want to encourage/force use of a stable version, or * if unstable versions are fine.

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.