PAIR-code / PAIR-code/deliberate-lab
Test Python against proposed PR code as part of standard CI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 96
- Forks
- 40
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 20
Description
Currently, our ci.yaml builds an runs the TypeScript code as well as our test suites. It also checks the generated Python schema.
However, it's still possible for types defined in TypeScript to become incompatible with Python, as seen in #1115. Somehow we should check the Python behavior against the TypeScript types to identify these kinds of problems at PR time, pre-merge.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/ci.yaml and review issue #1115 to understand the TypeScript/Python incompatibility this check should catch. Determine how the existing generated Python schema and test suites run, then add a pull-request CI check that compares Python behavior with the TypeScript types before merge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100