Framework: Laravel Container Why should we rely on illuminate/contracts

Created on 28 Sep 2017  路  2Comments  路  Source: laravel/framework

  • laravel 5.5

laravel container is very easy to use, But why should we depend on illuminate/contracts, Sometimes I do not want to use illuminate/contracts because it's too big

  • Auth
  • Broadcasting
  • Bus
  • Cache
  • Config
    ........(total 27 compontent interface)

Most helpful comment

There are many options, I have a few for you:
1) Don't use Laravel's container component, use a different one (there are many designed to be used separately), see here;
2) Stop complaining about a few files; a lot of packages don't even properly define their .gitattributes so you likely have hundreds (if not thousands) of extra files in your vendor folder already (such as tests, .editorconfigs etc);
3) Continue on your bandwagon against illuminate/contracts even though it clearly is designed to encompass the entirety of Illuminate and not just a singular component (don't be this guy).

All 2 comments

There are many options, I have a few for you:
1) Don't use Laravel's container component, use a different one (there are many designed to be used separately), see here;
2) Stop complaining about a few files; a lot of packages don't even properly define their .gitattributes so you likely have hundreds (if not thousands) of extra files in your vendor folder already (such as tests, .editorconfigs etc);
3) Continue on your bandwagon against illuminate/contracts even though it clearly is designed to encompass the entirety of Illuminate and not just a singular component (don't be this guy).

tks

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JamborJan picture JamborJan  路  3Comments

gabriellimo picture gabriellimo  路  3Comments

SachinAgarwal1337 picture SachinAgarwal1337  路  3Comments

iivanov2 picture iivanov2  路  3Comments

progmars picture progmars  路  3Comments