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

Fix issue #67 - New AssetStrategy #97

Merged
merged 13 commits into from
Nov 20, 2017
Merged

Fix issue #67 - New AssetStrategy #97

merged 13 commits into from
Nov 20, 2017

Conversation

svycka
Copy link
Collaborator

@svycka svycka commented Nov 16, 2017

added tests and some modifications to #93

I have a bad feeling that assemble() should be also stopped but not sure about this @basz ?

@svycka svycka added this to the v0.3.0 milestone Nov 16, 2017
@svycka svycka self-assigned this Nov 16, 2017
@svycka svycka requested a review from basz November 16, 2017 13:12
@coveralls
Copy link

Coverage Status

Coverage increased (+1.3%) to 82.368% when pulling b96965e on koseduhemak-master into 947a4cf on develop.

@svycka
Copy link
Collaborator Author

svycka commented Nov 16, 2017

Detector::assemble() is only used in LocaleUrl view helper I don't know what to do here my guess would be that no one would ever use this view helper for assets but if for any reason someone would do this should we stop our strategies execution?

/** @var array */
protected $file_extensions = [];

public function detect(LocaleEvent $event)
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

added because we don't want to run detect event on other strategies


// if the file extension of the uri is found within the configured file_extensions, we do not rewrite and skip further processing
if (in_array($extension, $this->file_extensions)) {
$event->stopPropagation();
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

will strop event propagation instead of returning false and handling one more response type, also does not require any changes in Detector... better? :D

@svycka
Copy link
Collaborator Author

svycka commented Nov 16, 2017

@basz if you don't see more problems I will merge this and release 0.3.0

@coveralls
Copy link

Coverage Status

Coverage increased (+1.3%) to 82.368% when pulling dee2829 on koseduhemak-master into 947a4cf on develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.3%) to 82.368% when pulling 1eb1e41 on koseduhemak-master into 947a4cf on develop.

@svycka svycka merged commit 225182b into develop Nov 20, 2017
@svycka svycka deleted the koseduhemak-master branch November 20, 2017 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants