Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

Seed Data - Make a Bunch of Project/Wp Seed Data using ChatGPT

Open
#2,430 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

back-end difficult
Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description

Note: The difficulty in this ticket comes not from the coding itself, but the volume of it that you'll have to do. I'm hoping it'll actually be a fun opportunity for someone to significantly shape the developer experience for all incoming devs.

Because seed data is pretty formulaic, it's a great opportunity to use ChatGPT to generate a bunch of seed data code, since it's all pretty similar. We need a lot of Project and Work Package Seed Data to test our features well (particularly our Gantt Chart feature). This ticket is to generate a sizeable amount of seed data using ChatGPT, so our local Gantt Chart looks much more similar in size to the production version.

Acceptance Criteria
  • At least 10 projects, with 1-3 work packages each have been added to the Gantt Charet (more variability is better, e.g. some project should have way more work packages, some less, some with different types of work packages, etc.)
Proposed Solution

You will likely discover a significant number of opportunities to abstract similar code into helper methods while doing this (for example, every work package, will need a change request to be associated with, and a change request to activate it, if we want it activated). You should wherever you can, abstract this type of code into helper methods, that we can use to make generating new seed data MUCH easier

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing TypeScript seed-data entry point and the current Project, Work Package, and Gantt Chart data. Add at least 10 projects with varied work-package counts and types, including the described change-request associations and activations; extract repeated generation into helpers where useful.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.