Steve Gray

Essentially the problem I'm having is that by having the controller class effectively a parameterless singleton, you can't then readily use faked 'thing' it talks to. You can work around...

I can't post actual examples as its work code: Ill mock an example when I'm at my desk in 90 minutes (it's 5am here ;)). The PR is basically clean-roomed...

Here's an es6'd controller, for example: ``` thing-doer.js class ThingDoer { constructor(widget) { this.widget = widget; } handlePutWidget(req, res) { if (!this.widget.exists(req.swagger.params.widgetKey.value)) this.widget.throb(req.swagger.params.widgetValue); } } module.exports = ThingDoer; somecontroller.js const...

I was also going to put in some ES6 promises support, but I suspect that's possibly going to muddy the waters - for example, if my controller needed to wait...

Hmm. Could do that _doh_! It'll trade in the ability to do dynamic discovery of modules though, but I can probably live with that.

The issue I'm having with the 'controllers' approach is that it expects inputs to be a function map of all resolved actions, so you can't just pass in a single...

This is absolutely one of the banes of my life too. I've got *dozens* of resources I want to preserve from accidental overwrites - such as DynamoDB tables. A pair...

Is there any documentation on what the metadata this is expecting is? -Steve

Hey @sagarp337 - Unfortunately I can't share our specific configuration, but what I can advise is: - Modify the demo list so that there's at least 8 rules in the...

@ravinitp - Found the issue. The _all_ is case sensitive in the prototype type, so if you set protocols "ALL", it gets replaced with "all" each type, and the OCI...