-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update list to include SS4 modules and modules in CWP 2.0 recipes #3
Update list to include SS4 modules and modules in CWP 2.0 recipes #3
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.
LGTM. There's some weird indentation in the JS file. @chillu would you mind taking a look over these amendments?
"type": "supported-module" | ||
}, | ||
{ | ||
"github": "bringyourownideas\/silverstripe-composer-update-checker", |
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.
Should those just be supported dependencies, with silverstripe-maintanence
as the supported module? This would allow us to provide the same functionality in a different way
"type": "supported-dependency" | ||
}, | ||
{ | ||
"github": "silverstripe-australia\/silverstripe-gridfieldextensions", |
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.
It's a bit hard to read this diff with both edits and ordering changes in the same commit (gridfieldextensions
is reintroduced later on in the diff)
"type": "supported-module" | ||
}, | ||
{ | ||
"github": "silverstripe\/silverstripe-dms-cart", |
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.
I guess we don't have a way to qualify "supported under CWP 1.x", right? It'll become clear by the lack of available CWP 2.x compatible releases
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.
We could, but we'd have to add yet another attribute to the list.
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.
We thought about doing this with semver constraints and dates and stuff but decided to go with a boolean 😆
"type": "supported-module" | ||
}, | ||
{ | ||
"github": "silverstripe\/silverstripe-graphql-devtools", |
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.
Why does this need to be supported?
modules.json
Outdated
"type": "supported-module" | ||
}, | ||
{ | ||
"github": "silverstripe\/silverstripe-moduleratings", |
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.
I don't this silverstripe-moduleratings
or silverstripe-moduleratings-plugin
need to be declared as supported
modules.json
Outdated
"type": "supported-module" | ||
}, | ||
{ | ||
"github": "silverstripe-australia\/silverstripe-multivaluefield", | ||
"github": "silverstripe\/silverstripe-mssql", |
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.
Nope, please don't add this.
This is adding a whole bunch of stuff to supported modules - some of them are obvious, some are judgement calls which we should discuss (e.g. |
Sorry about that. Given that this repo is used to generate the list of commercially supported modules on https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/, I'll just focus on the changes made to the latest version of that page. Modules added:
Modules Renamed:
Included Modules That Were Already Listed on silverstripe.org:
|
I've read through https://www.silverstripe.org/software/addons/supported-modules-definition/, and would suggest some changes to that list based on it. In particular, reclassifying some of this as a "supported dependency" with lessened expectations on our maintenance efforts. Maybe that's the case for some of the below already, can't tell from the list :)
|
They're dependencies of silverstripe/fulltextsearch, silverstripe/auditor and lekoala/silverstripe-debugbar |
5220f4f
to
97b14dd
Compare
@chillu Thanks for your feedback. I have changed the I have removed I added |
I published the latest version of the list to https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/ |
I'm hoping that by 5.0 we'll have a DB API that lets us extend the database classes properly without needing a proxy. I'll support the proxy modules until that time. |
Would it make sense to have a timestamp on when the list was last updated? |
Lookin' good! One question: Why is |
Good idea! I added a "timestamp" below the list featured on https://www.silverstripe.org/software/addons/silverstripe-commercially-supported-module-list/. If there is a better way to do this within the CMS, please let me know. |
@chillu, nice spotting! I will update |
97b14dd
to
01bfc0b
Compare
…ecipes Also introduce two new boolean attributes, scrutinizer and addons, to aid in displaying the table of modules. Deleted uncommented code. Link to addons page, rather than GitHub. Update links of repos that moved from GitLab to GitHub. Update references to silverstripe-australia, since renaming to symbiote. Retrieve badges directly from Scrutinizer where possible and display custom shield badge, where not possible.
01bfc0b
to
b22175a
Compare
Also:
Fixes https://github.com/silverstripeltd/cc-issues/issues/124