Guy's on-going/unfinished SilverStripe projects

projects.md

Projects & Ideas

On the go:

Crypto rewrite:

• PR: silverstripe/silverstripe-framework#8806 (draft)
• State: WIP - Needs tests made green, some regression testing and a peer review from someone

Constructor auto-DI

• PR: silverstripe/silverstripe-framework#8564
• PR: silverstripe/silverstripe-framework#9006
• PR: silverstripe/silverstripe-config#35
• State:
  • Awaiting merge
  • Might need some performance justification (run tests to ensure performance isn't seriously affected)

Dynamic storybook (Done):

• PR: silverstripe/silverstripe-admin#901
• State: Awaiting merge. Needs some documentation

Links module

• See: https://forum.silverstripe.org/t/new-links-module/1642
• Designs: https://projects.invisionapp.com/dsm/silver-stripe/silver-stripe/asset/components/5c4e6d24f3ad3830147691f6 (Sacha)
• Repo: https://github.com/ScopeyNZ/silverstripe-links
• State: Barely started.

Sync SS advisories with community DB

• Branch: https://github.com/creative-commoners/cow/tree/pulls/master/add-advisory-sync
• Description: Creates a PR to https://github.com/FriendsOfPHP/security-advisories after parsing https://www.silverstripe.org/download/security-releases/rss (on the command line). Asks you questions along the way as ss.org has less structured data than is required by FriendsOfPHP.
• State:
  • Mostly works - last run produced this PR: creative-commoners/security-advisories#7
  • Still generates some invalid shizzle that needs to be sorted out

"Adjustable Title Field" for Elemental:

• Branch: https://github.com/creative-commoners/silverstripe-elemental/tree/pulls/4.2/adjustable-title-field
• Designs: https://projects.invisionapp.com/dsm/silver-stripe/silver-stripe/asset/components/5c9c207ede91234535501a35 (Paul)
• State:
  • ~60% maybe
  • Does some crazy stuff where templates can be defined for the style, and it tries to use those templates to render a preview in the dropdown select
  • That previous bit might be too crazy - might have to remove that

Ideas:

• Get cow to show you more information about the changes in a module when releasing. See silverstripe/cow#134
• Write a SlackBot to send you travis (or CircleCI) artifacts (eg. Screenshots) via Slack when failures happen. Or at least send you a link to download them.
• Add better caching to SilverStripe's router. I think this is a good candidate for caching - it loops quite a bit with many routes. Symfony router and nikic/fast-route are good examples to learn from here.
• Write a whereExists API for the ORM. Sometimes WHERE EXISTS has a huge performance improvement over a join or WHERE (SELECT count()) > 0.
• Look into a debugger other than xdebug - there's one out there that supports stepping back
• Design the API for an Encryption service in framework (we have like 4 or 5 modules now that encrypt things)
• Go through and slap @method static create docblocks on anything that use Injectable. This is an acceptable contribution - see silverstripe/silverstripe-framework#8660
• Add page icons to TreeDropdownField: silverstripe/silverstripe-admin#232
• Rebuild (with new designs) the subsite selector dropdown in React: silverstripe/silverstripe-subsites#380
• Upgrade Babel in framework (maybe collab w/ Max's TypeScript endeavours)
• Convert GridFieldAddNewMultiClass (GridFieldExtensions) to React and then support it with the new "better button" in SS4.4+
• Add database table name generation to the upgrade tool: silverstripe/silverstripe-upgrader#162
• Remove SapphireTest extension on some tests that probably shouldn't need it. Switch to use the PHPUnit base test class instead. This may mean moving some tests that require fixtures into their own file. Candidate: ArrayListTest.
• Change JS injector to use have a configurable store: silverstripe/react-injector#3
• Write a dev API for things like showqueries and showtemplate. Have it togglable with GET vars or headers or cookies etc.
• Rewrite the Fluent locale dropdown in React (and move state to redux).