Skip to content

Conversation

@pyramation
Copy link
Contributor

@pyramation pyramation commented Dec 21, 2025

Summary

This PR replaces the legacy .questions.json/.js configuration format with the new .boilerplate.json/.js format for template scaffolding. It also switches tests to use a dedicated testing boilerplate repository for isolation.

Key changes:

  • Breaking: Removed support for .questions.json and .questions.js files
  • Added support for .boilerplate.json and .boilerplate.js as the new configuration format
  • Skip .boilerplate.json, .boilerplate.js, and .boilerplates.json from being copied to generated output
  • Changed test default repo from pgpm-boilerplates (production) to pgpm-boilerplates-testing
  • Updated tests and README documentation

Updates since last revision

  • Fixed failing CI by updating create-gen-app-test snapshots to reflect that .boilerplate.json is now correctly excluded from generated output
  • Snapshots also updated to reflect test:watch script change in the testing boilerplate repo (jest --watchjest --watchAll)

Review & Testing Checklist for Human

  • Verify the testing repo exists: Confirm https://github.com/constructive-io/pgpm-boilerplates-testing.git is set up and has the expected template structure
  • Check constructive repo compatibility: The template-scaffold.ts in constructive reads .boilerplate.json directly - verify it still works with these changes
  • Test with a real template: Run pgpm init with a template that uses .boilerplate.json to verify end-to-end functionality
  • Verify no production templates still use .questions.json: Since this is a breaking change, ensure all boilerplate repos have been migrated

Recommended test plan:

  1. Clone a workspace using pgpm init workspace
  2. Create a module with pgpm init using a template from the boilerplates repo
  3. Verify the generated output does NOT contain .boilerplate.json or .boilerplates.json files

Notes

  • The user explicitly requested no backward compatibility for .questions.json
  • The test repo change allows intentional test breakage without affecting production templates

Link to Devin run: https://app.devin.ai/sessions/718276b3817a4c70831019b07be99855
Requested by: Dan Lynch (@pyramation)

…format

- Replace .questions.json/.js support with .boilerplate.json/.js
- Skip .boilerplate.json, .boilerplate.js, and .boilerplates.json from output
- Update tests to use pgpm-boilerplates-testing repo for isolation
- Update README documentation for new format

BREAKING CHANGE: .questions.json/.js files are no longer supported.
Use .boilerplate.json/.js instead.

Co-Authored-By: Dan Lynch <[email protected]>
@devin-ai-integration
Copy link

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

…usion

- Remove .boilerplate.json from expected directory structure
- Update test:watch script to jest --watchAll

Co-Authored-By: Dan Lynch <[email protected]>
@pyramation pyramation closed this Dec 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants