-
As a CMS Squad, we don't want to carry forward code that is not needed to minimise our maintenance burden.
## Acceptance criteria
- [x] [`JSONField`](https://github.com/silverstripe/silverstripe-l…
-
Just a list of things I think Next (and the framework it is based on) should have. Feel free to append anything you think is important
- [PSR-0 compliance](https://github.com/php-fig/fig-standards/blo…
-
Currently most `GridFieldComponent` classes implicitly require some methods which are implemented on `DataObject` but not on `ViewableData`.
It is not uncommon to want to use a `GridField` with oth…
-
We don't currently have any automated checks to validate the quality of our documentation. This means we might potentially have now - or could easily introduce in the future - markdown formatting issu…
-
The following supported modules are missing the merge-ups CI action which should have been automatically created from this repo. That suggests that this repo is skipping them for some reason.
- htt…
-
SilverStripe foundational CMS UI technologies are 5-10 years old, and are largely based on an abandoned internal project by our former CTO (Entwine). In 2015, we've started removing this technical deb…
-
This is an automatically created issue used to list automatically createdjavascript pull requests every 3 months.
It was created by the `.github/workflows/js-prs-issue.yml` workflow in the [silvers…
-
Follow up to https://github.com/silverstripeltd/product-issues/issues/753
Currently only `silverstripe/framework` has a `.github/workflows/merge-up.yml` file which uses the new [gha-merge-up](https…
-
The LinkField never went through a full peer review process.
## Acceptance criteria
- A top down review of LinkField is performed.
- Potential problems or architectural decisions are highlighted.
- Q…
-
e.g. https://github.com/symbiote/silverstripe-advancedworkflow/actions
It's cos of the copy paste nature when originally adding the workflow https://github.com/symbiote/silverstripe-advancedworkflo…