Download the PHP package einenlum/iron without Composer

On this page you can find all versions of the php package einenlum/iron. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package iron

Iron

CircleCI Latest Stable Version Latest Unstable Version

A Carbon-like tool done the right way.

Install

composer require einenlum/iron:dev-master

Usage

Available methods

And every method (and getter) available in Carbon on the CarbonImmutable objects.

Why?

Carbon is a really useful tool. I'm just not really happy with the implementation they chose. Extending the native \DateTime class seems dangerous (here is some documentation about this problem in JS, but it works for PHP too). We should not extend the behavior of code we don't own. Also, being able to pass a Carbon object to a method waiting for a native \DateTime object, seems wrong to me.

Here we use Iron to manipulate data in a fluent API using an \ImmutableDateTime object under the hood and we finally return a native PHP \DateTimeImmutable (or \DateTime) object.

For now it just wraps carbon calls and getters. Next step will be for sure to implement here all the methods we need to get rid of Carbon in the end.

Tests

This project is tested thanks to PHPSpec and PHPUnit. To run the tests:

composer test

CS Fixing

Coding Standards are checked and fixed thanks to PHP-CS-Fixer. To fix your code, just run composer cs-fix.

Contributing

Please, feel free to contribute and improve this project.

License

MIT.


All versions of iron with dependencies

PHP Build Version
Package Version
Requires nesbot/carbon Version ^2.5
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package einenlum/iron contains the following files

Loading the files please wait ....