As a User, I want to specify complex routes including parameters and types.

[wdfox]

Context

In Azure Functions, route params are followed by their (possible) types. E.g. {category:alpha}. Currently, we are parsing from { to }, but we need to properly account for param types as well. This behavior would incorrectly parse the following route /create/{item:int}, identifying the route parameter as item:int rather than item of type int.

Tasks

• Move parseOperation to separate file #42
• Fix parseOperation behavior to handle param types #27
• Add tests for parseOperation #41

Success Criteria

When parsing operations, the script correctly identifies route parameters regardless of whether or not a param type is specified. Types are optional, so the parsing should work whether a type is provided or not.