-
Notifications
You must be signed in to change notification settings - Fork 1
feat: stache content pipe #56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces a pipe to automatically determine content locations, replacing the manual configuration of the content_path.
- Added a YAML fixture for a submission with sample text content.
- Added a YAML fixture for pages to support the new content detection mechanism.
Reviewed Changes
Copilot reviewed 4 out of 16 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tests/fixtures/content/submissions/1743066599.5568.yaml | New submission fixture with sample text content. |
| tests/fixtures/content/collections/pages.yaml | New fixture for pages defining a title and template as part of the new content system. |
Files not reviewed (12)
- config/backup.php: Language not supported
- phpunit.xml: Language not supported
- src/Pipes/Content.php: Language not supported
- src/Pipes/ContentStachePipe.php: Language not supported
- tests/Feature/RestoreBackupTest.php: Language not supported
- tests/Helpers.php: Language not supported
- tests/TestCase.php: Language not supported
- tests/Unit/BackuperTest.php: Language not supported
- tests/Unit/ChunkyTest.php: Language not supported
- tests/Unit/PipeTest.php: Language not supported
- tests/Unit/RestorerTest.php: Language not supported
- tests/Unit/ZipperTest.php: Language not supported
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces the new StacheData pipe to replace the existing Content pipe, improving the automated resolution of content paths and reducing configuration overhead.
- Updated fixture data for pages in tests.
- Revised documentation in pipeline.md to reference the new StacheData pipe.
- Modified the Logs backup and restore method signatures, including adding readonly to the Logs class.
Reviewed Changes
Copilot reviewed 5 out of 21 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| tests/fixtures/content/collections/pages.yaml | Adds fixture data for pages to support content backup testing. |
| docs/pages/pipeline.md | Updates pipeline examples and adjusts method signatures in Logs. |
Files not reviewed (16)
- config/backup.php: Language not supported
- phpunit.xml: Language not supported
- src/Abstracts/BackupPipe.php: Language not supported
- src/Pipes/Assets.php: Language not supported
- src/Pipes/Content.php: Language not supported
- src/Pipes/StacheData.php: Language not supported
- src/Pipes/Users.php: Language not supported
- tests/Feature/RestoreBackupTest.php: Language not supported
- tests/Helpers.php: Language not supported
- tests/SkippingPipe.php: Language not supported
- tests/TestCase.php: Language not supported
- tests/Unit/BackuperTest.php: Language not supported
- tests/Unit/ChunkyTest.php: Language not supported
- tests/Unit/PipeTest.php: Language not supported
- tests/Unit/RestorerTest.php: Language not supported
- tests/Unit/ZipperTest.php: Language not supported
This PR adds a pipe that is intended to supersede
Itiden\Backup\Pipes\Content.This pipe will know where your content is so users wont have to configure it. And we can remove the
content_pathconfig value.content_path...