Skip to content
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

API Split SilverStripe\Assets into separate module #6723

Merged
merged 1 commit into from Mar 22, 2017

Conversation

tractorcow
Copy link
Contributor

@tractorcow tractorcow commented Mar 20, 2017

@sminnee sminnee added this to the CMS 4.0.0-alpha6 milestone Mar 21, 2017
Copy link
Member

@sminnee sminnee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 small change

@@ -23,6 +23,7 @@
"monolog/monolog": "~1.11",
"nikic/php-parser": "^2 || ^3",
"silverstripe/config": "^1@dev",
"silverstripe/assets": "^1@dev",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a requirement of cms, not framework.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK while there's coupling still in place this is probably okay as a first step.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, there is quite a bit of work to de-couple that at this stage. It may be closer to a 5.0 / 4.late goal. :)

@@ -23,6 +23,7 @@
"monolog/monolog": "~1.11",
"nikic/php-parser": "^2 || ^3",
"silverstripe/config": "^1@dev",
"silverstripe/assets": "^1@dev",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK while there's coupling still in place this is probably okay as a first step.

@sminnee
Copy link
Member

sminnee commented Mar 21, 2017

@silverstripe/core-team any objections?

Copy link
Contributor

@flamerohr flamerohr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will FileField stay in framework?
I guess it's one of those cross-dependency/coupling issues you guys were talking about

Copy link
Member

@kinglozzer kinglozzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No objections from me

Copy link
Contributor

@stevie-mayhew stevie-mayhew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from the already mentioned coupling issues with some of the trickier parts of the system this looks like a great first step.

@sminnee
Copy link
Member

sminnee commented Mar 22, 2017

I feel like we've got a sufficient quorum so I'm merging!

@sminnee sminnee merged commit d91c665 into silverstripe:master Mar 22, 2017
@tractorcow tractorcow deleted the pulls/4.0/assets-module branch March 23, 2017 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants