This website requires JavaScript.
Explore
Help
Sign In
sartography
/
cr-connect-workflow
Watch
1
Star
0
Fork
0
You've already forked cr-connect-workflow
mirror of
https://github.com/sartography/cr-connect-workflow.git
synced
2025-02-22 20:58:28 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
cr-connect-workflow
/
crc
History
Dan Funk
534e8493a4
Deleting was broken because statistics were causing an integrity constraint.
...
Updating IDS bpmn to the latest for testing. Adding a TODO
2020-04-02 12:58:52 -04:00
..
api
Deleting was broken because statistics were causing an integrity constraint.
2020-04-02 12:58:52 -04:00
models
Deleting was broken because statistics were causing an integrity constraint.
2020-04-02 12:58:52 -04:00
scripts
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
2020-03-30 08:00:16 -04:00
services
fixing a bug that was causing failing tests.
2020-03-30 14:01:57 -04:00
static
Deleting was broken because statistics were causing an integrity constraint.
2020-04-02 12:58:52 -04:00
__init__.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
api.yml
fixing a bug that was causing failing tests.
2020-03-30 14:01:57 -04:00