michaelquigley / cf Goto Github PK

Explore global resource wiring using cf.Resource.

The current implementation of variable handling in the Cf framework only supports a single ${variable}, or no variables at all. This works well to allow variables to return types other than string.

Within strings, we're probably going to want to be able to /support/${multiple}/${variables}.

Support "aliases" for fields in the data.

cf.StoreYaml, the opposite of cf.BindYaml.

Probably should also include cf.Store, which can produce the intermediate map[string]interface{}.

nil field pointers seem to cause issues for cf.Dump.

Create arrays of FlexibleSetter (interface{}) types.

Implement idiomatic enum type dumping.

It would be useful to optionally error from Bind when unmapped data is present.

When whole number data is presented to a float64 field, a mapping failure occurs.

Implement a registry for globally-scoped objects available for system wiring.

Implement support for dumping flexible interface{} fields.

type Cfg struct {
    Instances []interface{}
}

The flexible setter will be passed the entire array of data elements for each Instances invocation, rather than the indexed data element.

Implement access to struct fields through idiomatic obj.field selection keys.

See if there is a variable syntax that could be incorporated int Cf, along with a "resolver" infrastructure, which can allow variables to resolved externally.

Then, in data, a string value, which takes the form ${variableName} would be resolved by Cf externally, before being inserted into the bound object.

Iterate on the core binding implementation for v0.2.x.