Closed robbieaverill closed 6 years ago
Hey @robbieaverill If there's a better forum for this question, then let me know, but what namespace and dir structure were you thinking of using?
I'm about to use the following (open to suggestions though)
/home/russellmichell/htdoc/tdc.govt.nz/cwp-core/src Atom/ (CwpAtomFeed.php) Config/ (CwpInitialisationFilter.php) Extension/ (everything that was under "extensions") Model/ (everything that was nder "models") Report/ (CwpStatsReport.php) Search/ (CwpSolrConfigStore.php, CwpSolr.php)
Hey @phptek - this is the perfect forum for this!
The folder structure looks good to me.
I suggest we use CWP\Core
as the namespace for this module. We'll use CWP\CWP
for github.com/silverstripe/cwp.
What do you think?
For the namespace CWP\Core
is precisely what I had just used.
Don't forget to use the silverstripe-upgrader tool, or manually create a .upgrade.yml
file if you don't want to use it
@robbieaverill I've had probs with the upgrader (composer related) and TBH I CBA (Google that one!) I figure I'm going to be in each file anyway so...
I'm going to work against @phptek's fork which has he's been doing great work on so far, and we will make a PR back to master when it's ready
Remaining is to sort out the TinyMCE plugins that have been removed from core in SS4
Pull requests list in the description above updated
Use namespace
SilverStripe\CWPCore
CWP\Core
.Sub-tasks can be added separately or as items in a checklist on this issue.
Acceptance criteria
.tx
file has been removed from SS3 branches and merged up (SS)Sub tasks