Nick Lucas

Currently the IEEE standard is enforced, where operands must come after everything else. it is quite common on CLIs to support operands coming before options. we should support this to...

Not the most common type, and some work on the help generator may be needed for option value structure

Support OptionParameter/Operand data validation

1

Such as Range(0, 60) for numbers, Regex() validation, etc. This is a nice to have, although quite easy to do by the application developer, and potentially more flexible that way.

Something like: ``` C# BeanField field = bean.GetField("some_int"); field.FieldName; // out: "field_name" field.DBType; // out: Int32 field.Value; // out: "7" ``` Can behave like `Nullable` where treating it like a...

It makes sense that we don't allow a standard Bean to be returned as that would infer that use of Store() or Trash() are valid. The RowToBean method is therefore...

Right now we can make multiple requests to the database and get related objects and code this into Bean subclasses, but one of Limebean's best features is you don't need...

https://github.com/Nick-Lucas/LimeBean/pull/3/commits/00f2324feac2c6737b78aaad29b368d7bc332b31 If the database will always re-convert any of our conversions back to the correct type of the field, we should only bother attempting conversions such as this when in...

BeanAPI.Store(...) returns an Object, which contains the Primary Key. Consider whether this could be a specific usable class instead of 'Object'

We should consider throwing an exception when the column doesn't exist as this can be the source of invisible bugs in user applications.

This may be more than a feature of FluidMode. Adding support for automatically managing these columns at the BeanAPI or Bean level as a setting, like .Keys() does for PKs,...