Duncan Jones

Decision is to have each parameter added as its own event ( [ClassifierRequestParameterSet.cs](https://github.com/MerrionComputing/EventsSourcing-on-Azure-Functions/blob/master/src/EventSourcingOnAzureFunctions.Common/CQRS/ClassifierHandler/Events/ClassifierRequestParameterSet.cs) ) - this allows for reaction to a particular parameter and also reduces the risk of the...

Interestingly if I explicitly set it in the local.settings.json file I get the message: > Skipping 'WEBSITE_AUTH_ENCRYPTION_KEY' from local settings as it's already defined in current environment variables.

I think a blob file with file name being e.g. snapshots/projection/{domain}/{entity}/{projection name}/{instance key}.{as of sequence number} would make the most sense as a naming standard? (Then just have the content...

I think I will hold off doing this until the project is out of pre-release

Currently failing with > Cannot bind parameter 'writeContext' to type IWriteContext. > Make sure the parameter Type is supported by the binding. > If you're using binding extensions (e.g. Azure...

Needs to be on a per **Domain** basis so command handlers can be set up to watch a single domain.

Each _command_ is backed by an event stream

The life cycle for a command should be something along the lines of:- - Creation - Parameter(s) set - Validations performed - Action step(s) performed At any stage the current...

**Projections required:-** 1. Command parameters - because parameters can be added or changed while the command is in flight (by the command handler itself usually) it is handy to be...

Question: should there be an explicit "Command Complete" event?