Skip to content

addTags on TagHandler #171

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

Merged
merged 3 commits into from
Feb 13, 2015
Merged

addTags on TagHandler #171

merged 3 commits into from
Feb 13, 2015

Conversation

dbu
Copy link
Contributor

@dbu dbu commented Feb 7, 2015

follow up of #162

This allows TagHandler to track tags. I tried adding a flush method that calls header() but feel there is little value to that. See the doc diff for how i propose to use this outside symfony.

* This must be called before any response is sent to the client.
* Make sure this is called after all addTags calls and only once.
*/
public function flushTags()
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is for the library only, in the bundle we will have something using Response.

@dbu dbu force-pushed the tag-http-response branch from 5a8c64a to 3530c26 Compare February 8, 2015 10:14
@dbu dbu force-pushed the tag-http-response branch from 3530c26 to c617cd6 Compare February 8, 2015 10:17
The tag handler helps you to invalidate all cache entries that where marked
with a specified tag. It works only with a ``CacheInvalidator`` that supports
``CacheInvalidator::INVALIDATE``.
.. versionadded:: 1.3
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this does not render as nicely as expected, because our sphinx setup does not load basic.css but only theme.css - @ddeboer would you know why we do not load default.css and what i could do to get the

.versionmodified {
    font-style: italic;
}

into our css, or load basic.css?

Copy link
Member

Choose a reason for hiding this comment

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

We use the Read the Docs theme (theme.css) on local builds too, so you can see what it will really look like. Unfortunately, they don’t support the version directives. Pushed a commit that adds some basic formatting for versionadded/versionchanged.

@dbu
Copy link
Contributor Author

dbu commented Feb 8, 2015

i propose we bump the branch-alias to version 1.3 and tag 1.3.0-alpha1 after merging this. then i can work on the bundle and once that is good and we need no further tweaks on TagHandler, we can tag 1.3.0 stable.

ddeboer added a commit that referenced this pull request Feb 13, 2015
@ddeboer ddeboer merged commit 59a0bcf into master Feb 13, 2015
@ddeboer ddeboer deleted the tag-http-response branch February 13, 2015 12:11
@ddeboer
Copy link
Member

ddeboer commented Feb 13, 2015

Merged and... whoops, tagged 1.3.0 stable already. ;) Let’s hope you don't need changes to TagHandler, otherwise jumping to 1.4.0 shouldn’t be a problem.

@dbu
Copy link
Contributor Author

dbu commented Feb 13, 2015

cool, thanks!

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.

2 participants