Skip to content

Conversation

@leewillis77
Copy link
Contributor

A rather big commit, most is just whitespace / doc / escaping fixes. The fourth commit should resolve the issue originally reported in #152. Could do with a second pair of eyes to check there aren't unwanted side effects though.

Copy link
Member

Choose a reason for hiding this comment

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

These should be refactored to use the checked() function

Copy link
Member

Choose a reason for hiding this comment

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

Awesome, thanks for using checked()!

The last thing we need here is to make sure we're not introducing any regressions - we've recently had some bugs fixed in this area of pagination, I want to make sure we're not re-breaking them.

@JustinSainton
Copy link
Member

The test cases to ensure we're not regressing (aside from #152) are #324, #134 and possibly others.

Copy link
Contributor

Choose a reason for hiding this comment

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

Did the "" get inadvertently escaped?

Copy link
Member

Choose a reason for hiding this comment

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

It is intended to be escaped, as it's displaying the code.

@JustinSainton JustinSainton modified the milestones: Future Release, 3.9.0 May 3, 2014
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.

3 participants