cr-connect-workflow/crc/api
Dan Funk 55a1850e7c adding a navigation component to the Workflow Model.
running all extension/properties through the Jinja template processor so you can have custom display names using data, very helpful for building multi-instance displays.
Properties was returned as an array of key/value pairs, which is just mean.  Switched this to a dictionary.
2020-05-14 13:43:23 -04:00
..
__init__.py Adding file management. Files are stored in the database along with basic meta data. 2019-12-27 13:50:03 -05:00
common.py Vastly more informative ApiError model that provides details on the underlying task where the error occured. 2020-03-27 08:29:31 -04:00
file.py No longer requires task_id 2020-05-06 14:27:28 -04:00
study.py Refactor the stats models, and assure they are very correct across all tests with the workflow api. 2020-05-04 10:57:09 -04:00
tools.py Adding a simple endpoint that describes what scripts are currently available, along with a brief description. 2020-03-03 15:30:42 -05:00
user.py It became impossible to use the Swagger ui when we started adding authentication to all of the calls. I discovered Connexion and Swagger have a default way of handing JTW authentication and this cleans up our code quite a bit, moves the securing of endpoints into the API Definition, which is quite nice, and removes a whole library dependency (I never get to do that!) I added a SWAGGER_AUTH_KEY that can be used in non-production environments to allow users to quickly authenticate from the Swagger ui. I also removed all api calls to simple little happy api services, because that is just mean and pointless. 2020-03-24 14:15:21 -04:00
workflow.py adding a navigation component to the Workflow Model. 2020-05-14 13:43:23 -04:00