Arthur Mingard
Arthur Mingard
@developit I'll run some tests. It could prove benificial to introduce some acceptance tests ontop of the current unit tests.
@iwazaru it looks like you haven't created a config. If you continue through the readme to the [*Configuration*](https://github.com/dadi/cdn#configuration) section you'll find instructions and a link to the docs site.
Nice! I was seeing that as a separate webapp, similar to Publish. The checklist page was more of basic kickstart checklist.
@danwdart Some of the features listed here can be handed with http://github.com/dadi/cli although it would be nice to offer a configuration app. Perhaps something to consider for the API dApp?
No immediate requirement. Should we find a place to break out plugin requests?
@eduardoboucas Currently yes, but potentially not in the future, depending on roadmapped decisions around the remit of api. @josephdenne @jimlambie thoughts?
@abovebored @jimlambie and @josephdenne as discussed yesterday. @eduardoboucas hooks question for you :)
Yes I prefer the idea of being part of `validation`.
I like the DB-level concept. Is such a concept supported by all the current Edge DB modules? Maybe the unique index would be better. Again, if 100% coverage with DBs.
Would that increased load be more or less than a pre-save match query on every unique field? I'm happy with either but perhaps we should test both?