Generating TAFFY from Swagger \ OpenAPI

[Michael Collins]

So I posted about taking Taffy to Swagger, now I am looking at going the other way.  Swagger to Taffy code.

Swagger supports defining many taffy:uri to each 'get' method, so I am wondering how this translates to Taffy.  Does that mean I need a 3 CFCs like the attached image shows.

Does taffy support something like this - this would be equivalent to the restpath attribute in cffunction inside CF REST.

I see taffy has 3 things at the function level taffy:verb,taffy:mime and taffy:default but nothing like path.  

Thanks,

Mike

[Michael Collins]

I have since found this post raising the same question.

https://groups.google.com/forum/#!searchin/taffy-users/path%7Csort:relevance/taffy-users/jY7ZoV2nZeQ/o5pjlRBxWn8J

That answers my question, just wanted to make sure I was not missing anything.

Mike

[Adam Tuttle]

I'm on mobile and that deep link isn't working in the mobile friendly Google groups UI, so I'm winging it.

Long story short, each distinct URI is its own component in Taffy's opinion. There is component level metadata to set this.

Any code generator should generate one CFC per URI.

HTH,

Adam

--
You received this message because you are subscribed to the Google Groups "Taffy Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taffy-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.