Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PONY-24 fix response handling for content types that contain application/json #12

Merged
merged 1 commit into from
May 4, 2022

Conversation

ckoegel
Copy link
Contributor

@ckoegel ckoegel commented May 4, 2022

No description provided.

@ckoegel ckoegel requested a review from ajrice6713 May 4, 2022 19:41
@ckoegel ckoegel merged commit da58fd4 into PONY-16 May 4, 2022
@ckoegel ckoegel deleted the PONY-24 branch May 4, 2022 19:42
ckoegel added a commit that referenced this pull request May 5, 2022
* Create newSchema.yml

Took 18 minutes

* rework schema to YAML and update to new format

* Remove Core reference from pypony.py

Took 25 seconds

* Update requirements.dev.txt

Took 34 seconds

* unused import

Took 3 minutes

* fixing schema rework

* more fixes of schema

* temporary stop until we figure out validation

* Added some TODOs

Figured out how to fix `check_endpoint_coverage()`

Took 15 minutes

* Add some TODOs

* Get the validation working

Took 1 hour 0 minutes

* PONY-19 Fix `context_test.py`

Took 6 minutes

* fix request test

* PONY-25, PONY-22, PONY-27 Fix `step_test.py`, `preprocessing_test.py` and Endpoint Coverage (#11)

* begin fixing localhost step files for preprocessing test

* fix operation coverage

* fix step files and get preprocessing_test.py and step_test.py to work

* remove all references to `endpoint`

* remove more references to `endpoint`

* fix response handling for content types that contain `application/json` (#12)

* PONY-26 fix `validate_test.py` (#13)

* finish fixing the last of the tests (#14)

* cleanup unused imports

* remove local files

Co-authored-by: AJ Rice <53190766+ajrice6713@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant