Merged
Conversation
Member
|
In regards to the question in the description, I think it would be better that ActiveAdmin didn't render all/any filters by default, instead it would have to be specified explicitly in the file. I've had trouble in the past leaving the defaults so I've been in the habit of always specifying filters on all pages. |
This file contains hidden or 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
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.
After enabling a sample nested resource in #5814, I found a crash in the users page, when filtering by post.
I guess this kind of filtering is pretty uncommon (it always results in a single record), maybe it shouldn't be included by default?
Anyways, this should fix the crash, which by the way looks like this: