NYCPlanning / NYCPlanning/data-engineering
Ergonomics around dev container, "optional" local setup dependencies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Bit of a stub, but wanted to follow up to #1726, which was well-intentioned but doesn't quite solve the issue at hand. As @alexrichey pointed out, these resources aren't inherently tightly-coupled to the pytests, but are more part of a dev setup. Still ideally need to make it semi-ergonomic to use with or without the dev container itself, but before any work we should actually just sit down and brainstorm some requirements of what this stuff looks like in a semi-ideal state
Contributor guide
No contributing guide indexed for this repository
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 by reviewing issue #1726 and the current dev-container, local setup, and pytest resources. The issue first calls for brainstorming requirements for using these resources with or without the dev container; done would be an agreed semi-ideal setup design before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100