Add `PlanSteps` Table with Migration and TRPC Router Integration

[kleneway]

Description

Introduce a new PlanSteps table to manage and track the detailed steps associated with each project issue. Additionally, implement a corresponding TRPC router to facilitate CRUD operations on the PlanSteps data.

Table Schema

Create a PlanSteps table with the following columns:

• id (UUID, Primary Key): A unique identifier for each plan step.
• projectId (UUID, Foreign Key): References the associated project in the Projects table.
• issueNumber (Integer): The number of the issue this plan step is linked to.
• stepNumber (Integer): The sequence number of the plan step within the issue.
• details (String): Detailed description of the plan step.
• filePath (String): Path to the file to be created or edited as part of the plan step.
• isActive (Boolean): Indicates whether the plan step is currently active.
• createdAt (Timestamp): Timestamp of when the plan step was created. Use ...timestamps
• updatedAt (Timestamp): Timestamp of the last update to the plan step. Use ..timestamps

Be sure to research how other tables are created using this specific version of orchid ORM.

Migration

• Create Migration File: Add a new OrchidORM migration script named create_plan_steps_table following the naming convention used in existing migrations. Be sure to research other migrations to understand exactly how to format this file. The name should be unique and ideally a timestamp from today (10/08/2024).
• Implement Schema: Use the defined table schema to implement the PlanSteps table in the migration.

TRPC Router

• Create Router File: Add a new TRPC router file named planStepsRouter.
• CRUD Operations:
  • Create: Add a function to create a new plan step.
  • Read:
  • Fetch all plan steps for a given projectId and issueNumber.
  • Fetch a single plan step by id.
  • Update: Update fields of a plan step except for projectId and issueNumber.
  • Delete: Mark a plan step as archived by setting isActive to false.
• Reorder Steps: Implement a function to reorder plan steps. The function should accept an array of PlanStep IDs in the desired order and update the stepNumber accordingly in the database.
• Integrate with Main Router: Import and add the planStepsRouter to the main TRPC router root (./routers/index.ts).

Validation and Constraints

• Input Validation: Ensure all TRPC endpoints validate inputs, such as checking for valid UUIDs and required fields.
• Constraints: Prevent updates to projectId and issueNumber fields during plan step modifications.

Testing

• DO NOT create any tests for this issue

References

• Existing Migrations: Refer to the create_tasks_table migration for structure and implementation examples.

Acceptance Criteria

• The PlanSteps table is created with all specified columns and constraints.
• The migration runs without errors and integrates seamlessly with existing database structures.
• The TRPC router provides all required CRUD functionalities and the reorder feature.

@jacob-ai-bot

[jacob-ai-bot[bot]]

JACoB here...

You mentioned me on this issue and I am busy taking a look at it.

I'll continue to comment on this issue with status as I make progress.

[jacob-ai-bot[bot]]

Unfortunately, I ran into trouble working on this.

Here is some error information:

Command failed: __NEXT_TEST_MODE=1 SKIP_ENV_VALIDATION=1 npm run build --verbose && npx tsc --noEmit
npm verb cli /opt/render/project/nodes/node-20.11.0/bin/node /opt/render/project/nodes/node-20.11.0/bin/npm
npm info using npm@10.2.4
npm info using node@v20.11.0
npm verb title npm run build
npm verb argv "run" "build" "--loglevel" "verbose"
npm verb logfile logs-max:10 dir:/opt/render/.cache/_logs/2024-10-08T20_20_48_703Z-
npm verb logfile /opt/render/.cache/_logs/2024-10-08T20_20_48_703Z-debug-0.log
npm verb cli /opt/render/project/nodes/node-20.11.0/bin/node /opt/render/project/nodes/node-20.11.0/lib/node_modules/npm/bin/npm-cli.js
npm info using npm@10.2.4
npm info using node@v20.11.0
npm verb title npm run build:1-next
npm verb argv "run" "build:1-next"
npm verb logfile logs-max:10 dir:/opt/render/.cache/_logs/2024-10-08T20_20_49_121Z-
npm verb logfile /opt/render/.cache/_logs/2024-10-08T20_20_49_121Z-debug-0.log
Killed
npm verb exit 137
npm verb code 137
ERROR: "build:1-next" exited with 137.
npm verb exit 1
npm verb code 1

[jacob-ai-bot[bot]]

JACoB here...

You mentioned me on this issue and I am busy taking a look at it.

I'll continue to comment on this issue with status as I make progress.

[jacob-ai-bot[bot]]

Update

I've completed my initial work on this issue and have created a pull request: JACoB PR for Issue Add PlanSteps Table with Migration and TRPC Router Integration.

The changes currently result in an error, so I'll be making some additional changes before it is ready to merge.

[jacob-ai-bot[bot]]

Update

I've updated this pull request: JACoB PR for Issue Add PlanSteps Table with Migration and TRPC Router Integration.

The changes currently result in an error, so I'll be making some additional changes before it is ready to merge.

[jacob-ai-bot[bot]]

Update

I've updated this pull request: JACoB PR for Issue Add PlanSteps Table with Migration and TRPC Router Integration.

The changes currently result in an error, so I'll be making some additional changes before it is ready to merge.

[jacob-ai-bot[bot]]

Update

I've updated this pull request: JACoB PR for Issue Add PlanSteps Table with Migration and TRPC Router Integration.

The changes currently result in an error, so I'll be making some additional changes before it is ready to merge.