mulesoft/osprey-cli

There should be a "strict" mode that turns mocking off and that warns of any routes that do not have an overriding handler

dmartinezg opened this issue · 3 comments

There should be a "strict" mode that turns mocking off and that warns of any routes that do not have an overriding handler

I should also warn of any Osprey registered routes (using api.get() or such) that are no in the RAML file.

There is no warning for routes that are not on the RAML files, that should be a blunt error straight forward. We do not indent to allow declaring routes that are not on the RAML, at least no using Osprey. You can do so directly via express thou.

Closing.

There is an enhancement for this topic on Osprey at mulesoft/osprey#23.