Swagger API Inconsistency
-
- Posts: 8
- Joined: Tue Sep 02, 2014 3:32 pm
- Bot?: No
Swagger API Inconsistency
Is the swagger API documentation still actively updated? I ran into some issues with some settings for timers such as their initial value when using the auto generated libraries from Swagger codegen. I realized it's because the Timer model used by the State API is actually different than the Timer model used by the Timer API, but both are documented using the Timer API definition. For the State API, the Timer members are 'used', 'display', 'count_up', 'init', and 'preserve'. In the Timer API, the members are 'name', 'value', 'on', 'enabled', and 'count_up'. I believe I can make the necessary changes to the spec to keep my development going, but figured I would point out the discrepancy so that it could potentially be fixed for the wider public.
-
- Posts: 8
- Joined: Tue Sep 02, 2014 3:32 pm
- Bot?: No
Re: Swagger API Inconsistency
Also, the "output" member in the "ramp" structure is also incorrect in the documentation. Based on what is returned by the bcs when polling a state, it should be a list of ints named "outputs".
-
- Posts: 9
- Joined: Mon Feb 12, 2018 12:06 pm
- Bot?: No
Re: Swagger API Inconsistency
What url did you use to get the swagger? The one in the docs doesn't seem to load anything.
Re: Swagger API Inconsistency
Move, copy, clear proc/states: http://manipulator.from-ca.com/
Perform coeff. mods: http://calculator.from-ca.com/
HMI latest ver: http://bbrally.altervista.org/guibeta/i ... r=01042020
Perform coeff. mods: http://calculator.from-ca.com/
HMI latest ver: http://bbrally.altervista.org/guibeta/i ... r=01042020