Revert "Sample Data Loading and Test in GitHub Action"

[palisadoes]

Reverts #3223

Summary by CodeRabbit

• New Features

  • Consolidated the sample data import process into a single, unified command for easier execution in development environments.

• Documentation

  • Updated and restructured developer guides to clarify the steps for importing sample data, now involving an interactive container session.
  • Removed redundant instructions for resetting the database to streamline the documentation.

• Chores / Refactor

  • Simplified container environment configuration by eliminating version-specific settings.
  • Removed outdated scripts and associated tests, consolidating database management functionality.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request makes several coordinated changes across the repository:

• A commented-out "Import-Sample-Data" job is added to the GitHub Actions workflow.
• The Dockerfile is simplified by removing Node.js version–specific environment variables.
• Developer documentation is updated by removing database reset instructions and clarifying the sample data import procedure.
• The package.json file now includes new dependencies and replaces multiple database management scripts with a single import command.
• Several legacy DB management scripts and their tests are removed while a new script for loading sample data is added.
• The Vitest configuration is adjusted by removing a custom timeout setting.

Changes

File(s)	Change Summary
.github/workflows/pull-request.yml	Added a commented-out "Import-Sample-Data" job section outlining steps for checking out the repo, setting up the environment, building a Docker image, and running a data import command (inactive by virtue of being commented out).
docker/api/Containerfile	Removed environment variable declarations (NODE_VERSION and extended PATH) related to Node.js, leaving a simplified configuration using only fnm.
docs/.../testing.md, docs/.../installation.md	In testing.md: Removed the section on resetting the database. In installation.md: Restructured the sample data import section with an updated command (pnpm run import:sample-data), instructions to open an interactive bash session, and a step to exit post-import.
package.json	Added dependencies: dotenv@^16.0.3, inquirer@^12.4.1, uuid@^11.0.5; replaced scripts reset:db and add:sample_data with a single import:sample-data command pointing to a new script.
scripts/dbManagement/*.ts, test/scripts/dbManagement/*.ts	Removed several legacy database management scripts (addSampleData.ts, helpers.ts, resetDB.ts) and their associated test files, eliminating functions and tests related to database resetting and sample data insertion.
vitest.config.ts	Removed the testTimeout property from the test configuration, reverting to default timeout behavior.
src/utilities/loadSampleData.ts	Added a new script for handling sample data import; defines functions for listing sample data, formatting the database, inserting collections from JSON files, and verifying record counts.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant CLI as Command Runner
    participant Script as ImportSampleData Script
    participant DB as Database
    participant FS as FileSystem

    Dev->>CLI: Run "pnpm run import:sample-data"
    CLI->>Script: Execute loadSampleData.ts
    Script->>FS: List sample data files
    Script->>DB: Format database (if required)
    Script->>DB: Insert collections from sample data files
    Script->>DB: Check record counts after import
    DB-->>Script: Return status/results
    Script-->>CLI: Output import results
    CLI-->>Dev: Display final outcome

Loading

Possibly related PRs

• updated sample_data import script, docs updated, githhub action to test #3146: Introduces an "Import-Sample-Data" job in the GitHub Actions workflow, directly relating to the new commented-out section in this PR.
• Fix data importation #3212: Adds a new script for loading sample data, which correlates strongly with the functionality implemented in src/utilities/loadSampleData.ts.
• Revert "chore(deps): bump drizzle-seed from 0.3.0 to 0.3.1" #3122: Modifies the package.json file by updating scripts and dependencies related to sample data management, aligning with the changes made in this PR.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7e6ef15 and aa254ab.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (13)

• .github/workflows/pull-request.yml (1 hunks)
• docker/api.Containerfile (0 hunks)
• docs/docs/docs/developer-resources/testing.md (1 hunks)
• docs/docs/docs/getting-started/installation.md (1 hunks)
• package.json (2 hunks)
• scripts/dbManagement/addSampleData.ts (0 hunks)
• scripts/dbManagement/helpers.ts (0 hunks)
• scripts/dbManagement/resetDB.ts (0 hunks)
• src/utilities/loadSampleData.ts (1 hunks)
• test/scripts/dbManagement/addSampleData.test.ts (0 hunks)
• test/scripts/dbManagement/helpers.test.ts (0 hunks)
• test/scripts/dbManagement/resetDB.test.ts (0 hunks)
• vitest.config.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

1. We don't merge PRs with poor code quality.
   1. Follow coding best practices such that CodeRabbit.ai approves your PR.
2. We don't merge PRs with failed tests.
   1. When tests fail, click on the Details link to learn more.
   2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
   3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 232 lines in your changes missing coverage. Please review.

Project coverage is 48.04%. Comparing base (798e422) to head (aa254ab).
Report is 2 commits behind head on develop-postgres.

Files with missing lines	Patch %	Lines
src/utilities/loadSampleData.ts	0.00%	232 Missing ⚠️

Additional details and impacted files

@@                 Coverage Diff                  @@
##           develop-postgres    #3271      +/-   ##
====================================================
- Coverage             48.91%   48.04%   -0.88%     
====================================================
  Files                   457      455       -2     
  Lines                 34152    33942     -210     
  Branches                959      892      -67     
====================================================
- Hits                  16707    16308     -399     
- Misses                17445    17634     +189     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.