You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,13 @@
16
16
## Writing Code
17
17
18
18
1. Write some code and make sure it's covered by unit tests. All unit tests are in the `tests` directory and the file structure should mirror the structure of the source code in the `openapi_python_client` directory.
19
+
20
+
### Run Checks and Tests
21
+
19
22
2. When in a Poetry shell (`poetry shell`) run `task check` in order to run most of the same checks CI runs. This will auto-reformat the code, check type annotations, run unit tests, check code coverage, and lint the code.
23
+
24
+
### Rework end to end tests
25
+
20
26
3. If you're writing a new feature, try to add it to the end to end test.
21
27
1. If adding support for a new OpenAPI feature, add it somewhere in `end_to_end_tests/openapi.json`
22
28
2. Regenerate the "golden records" with `task regen`. This client is generated from the OpenAPI document used for end to end testing.
0 commit comments