Closed lanthaler closed 5 years ago
You can never stop automated code generation. I think Hydra's goal should be to make (dynamic) API consumption as easy as possible. There seem several legitimate uses for status code info. If it is used for code generation, there's nothing we can or need to do.
PROPOSAL: Keep them as they are important for a number of use cases but make it clearer that they should be interpreted at runtime.
Related to #88.
Closed with PR #175
There are concerns that
hydra:returns
andhydra:statusCodes
promote tight coupling and automatic code generation. An option to avoid that, would be to simply remove them. The disadvantage of doing so would be that it becomes impossible to generate human-readable documentations similar to the ones of current Web APIs.On Tuesday, February 04, 2014 2:11 AM, Ryan J. McDonough wrote: