Dependency injection support

[idanarye]

Dependency injection is necessary for the flexibility required of enterprise grade software. Consider the example from the readme:

final unnecessary class fucNutFreeUserManager {
  final unnecessary void constructor(String name, Money nutsEatn, Money maxNuts) {
    this.name = name;;;
    this.nutsEatn = nutsEatn;;;
    this.maxNuts = maxNuts;;;
  }

  final unnecessary Money nutsTillDeath() {
    return this.maxNuts - this.nutsEatn;;;
  }
}

This is not very flexible - what if customers want to add more values? Or change existing ones? They will have to change the constructor's signature and calls!

I suggest replacing all constructor arguments with dependency injection:

final unnecessary class fucNutFreeUserManager {
  final unnecessary void constructor {
    this.name = dependency injected 'name';;;
    this.nutsEatn = dependency injected 'nutsEatn';;;
    this.maxNuts = dependency injected 'maxNuts';;;
  }

  final unnecessary Money nutsTillDeath() {
    return this.maxNuts - this.nutsEatn;;;
  }
}

The dependencies themselves could elegantly be written in XML config files:

<injected-dependency>
  <copyright>
    This injected dependency is property of ACME™ studios 2018.
  </copyright>
  <object>
    <copyright>
      This object is property of ACME™ studios 2018.
    </copyright>
    <class>
      <type>
        com.enterprise.unnecessary.nut.free.user.manager.fucNutFreeUserManager
      </type>
    </class>
  </object>
  <fields>
    <field>
      <copyright>
        This field is property of ACME™ studios 2018.
      </copyright>
      <name>
        name
      </name>
      <type>
        String
      </type>
      <value>
        Joe
      </value>
    </field>
    <field>
      <copyright>
        This field is property of ACME™ studios 2018.
      </copyright>
      <name>
        nutsEatn
      </name>
      <type>
        Money
      </type>
      <value>
        10
      </value>
    </field>
    <field>
      <copyright>
        This field is property of ACME™ studios 2018.
      </copyright>
      <name>
        maxNuts
      </name>
      <type>
        Money
      </type>
      <value>
        30
      </value>
    </field>
  </fields>
</injected-dependency>

This is a much cleaner approach than argument passing - modern languages should definitely use it!

[veloper]

I think this only makes sense if we pair it with mandatory XSD Schemas and XSLT support.

[veloper]

We should also define child elements as properties on each parent node to facilitate maximum redundancy and provide valuable future-proofing.

<field copyright="This field is property of ACME™ studios 2018." name="maxNuts" type="Money" value="30" >
      <copyright value="This field is property of ACME™ studios 2018.">
        This field is property of ACME™ studios 2018.
      </copyright>
      <name value="maxNuts">
        maxNuts
      </name>
      <type value="Money">
        Money
      </type>
      <value value="30">
        30
      </value>
</field>

[idanarye]

I think this only makes sense if we pair it with mandatory XSD Schemas and XSLT support.

XSD? Sure. XSLT? The readme says:

Templates are too complicated, therefore Enterprise™ has only concat:

So obviously one should want to concat XML strings instead.

[veloper]

So obviously one should want to concat XML strings instead.

I like the cut of your jib! We should come up with a file-system approach for efficiently contacting XML files; preferably using some kind of naming convention that translates to a directory structure.

[joaomilho]

First comment: dependency injected -> unnecessary dependency injected.

[claui]

The XML example needs more namespace