Uh oh!
There was an error while loading. Please reload this page.
Client and Plan support - #36
Conversation
Rework contributed code to conform to existing standards.
msavy
commented
Apr 7, 2018
@outofcoffee Any idea which branch I should work against? Also just noticed a few bits I need to zap before merging, but please have a play and see if it works for you. |
msavy
commented
Apr 7, 2018
Declarative bits that are missing will be committed shortly |
msavy
commented
Apr 7, 2018
Now I can see that the CLI needs a couple of extra commands adding to enable plans to be added to APIs (i.e. non declarative) |
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
@pcornish what is your philosophy when it comes to error handling? For example, at the moment with certain list commands you just get an ugly exception. My thoughts are that we could parse the returned JSON and display the canonical message? What do you think. Or is this already meant to happen? e.g. vs (mocked up example) -- something better than a huge trace. I'm still not quite clear whether this is meant to be happening but it's b0rked or we should be relying on CLI-side validation (which seems a lot of work and maintenance in this circumstance). |
Behaviour seemed to have changed for some reason, so took opportunity to align dependencies with Apiman main project use the ser/deser feature to fix. Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
msavy
commented
Apr 11, 2018
Okay, was having an issue that turns out to be related to a bug in Maven 3.5.0's snapshot metadata. Will be pushing some more changes shortly, hopefully. |
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
msavy
commented
Apr 11, 2018
@pcornish I think your recent "exception cause" changes on apiman/apiman may have had an unintended side-effect of breaking the apiman-cli tests -- as some exceptions that were 404 are now showing as 500s. Investigating! |
msavy
commented
Apr 11, 2018
Reference for the above d9f95c2990f01197152c5d5f3ed855aca1ea5bc9 |
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
Signed-off-by: Marc Savy <marc@rhymewithgravy.com>
Hi @msavy. On latest master (e35c0f0) and develop (776a17e) the tests look OK. Here are the steps I ran (straight from the travis config file): If you have some specific tests you want me to look at let me know and I'll happily take a look. |
msavy
commented
May 26, 2018
@pcornish I reverted a PR on apiman/apiman itself as it was causing the unintended side-effects. |
outofcoffee
commented
May 26, 2018
Ah yes, sorry, I did see that :( |
Reworked jquantins work, but excluded the deepList stuff which needs some additional discussion.