Andrew Fawcett

This was spawned from another [issue 123](https://github.com/financialforcedev/fflib-apex-common/issues/123)... "I couldn't agree more of the need to centralize queries and leverage common field lists. Avoiding the missing field error at runtime is...

Write more Apex tests

3

Continue to expand out the tests in the /tests sub-folder and those in the sample apps.

Support ability to express the bind(MyClass.class).to(asJSON)

2

As recently pointed out in another related blog (cannot find it now?)... JSON deserialization has some benefits.

Make the c:injector Lightning Component read direct to native

2

In cases where no binding is found it might be preferable to have the injector redirect to the native UI for the given action... ?

Following my last [blog](https://andyinthecloud.com/2018/07/29/test-driven-development-mocking-and-force-di/) and the code samples in its summary.... I am wondering if an option for the Apex Injector to optionally require a binding if the binding reference...

https://github.com/google/guice/wiki/LinkedBindings

At present the Lightning c:injector outputs to console on error (unknown binding). Consider different options for this. Display something on screen, show toast, other options?

Improve the UI so that it creates a record and thus avoid having to programmatically create a record to experience the rest of the demo.

Update to use SObject. getPopulatedFieldsAsMap

4

You should be able to remove the JSON hack with this method instead, SObject.getPopulatedFieldsAsMap.