-
Notifications
You must be signed in to change notification settings - Fork 46
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 schema validation for sticky. #853
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still waiting on Travis to give the green light but this checks out locally when testing this out in PL. Thanks @charginghawk!
⚡ PR built on Travis and deployed a now preview here:
|
⚡ Sauce Labs Test for chrome Passed!Test Details
|
⚡ Sauce Labs Test for internet explorer Passed!Test Details
|
⚡ Sauce Labs Test for chrome Passed!Test Details
|
⚡ Sauce Labs Test for internet explorer Passed!Test Details
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, obviously an oversight, thanks @charginghawk
Summary
The wrong schema here will throw a 500 error when loading sticky with twig_debug enabled. This fixes it.
How to test
Enabled twig_debug. View a page with the sticky component. It doesn't return a 500 error.