Refactor widget base and add dropdown for exposed view filter.#31
Open
jazzdrive3 wants to merge 1 commit intodrupal-fancy:8.x-1.xfrom
Open
Refactor widget base and add dropdown for exposed view filter.#31jazzdrive3 wants to merge 1 commit intodrupal-fancy:8.x-1.xfrom
jazzdrive3 wants to merge 1 commit intodrupal-fancy:8.x-1.xfrom
Conversation
Member
|
Hey @jazzdrive3, that's really cool! Will look into it soon :) |
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
2 participants
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.
Previously, if you added an exposed filter on a view, it would be a textfield. Not great UX. This makes it a dropdown, populated by all of the view modes of the parent entity.
We can't limit it based on field settings. This could be improved, however, if the view mode restrictions moved from the field instance settings, to the field storage settings.