Add Layout Pages Controller #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sometimes we need content pages, sometimes we need layoutpages. For an
API consumer, using the Ransack API for this (`filter: {
layoutpage_true: "1" }`) is cumbersome and unintuitive. This adds a new
controller instead and limits the pages controller to content pages.
mamhoff
force-pushed
the
add-layout_pages_controller
branch
from
8dcac60 to
37bee80
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes we need content pages, sometimes we need layoutpages. For an
API consumer, using the Ransack API for this (
filter: { layoutpage_true: "1" }) is cumbersome and unintuitive. This adds a newcontroller instead and limits the pages controller to content pages.