Re-enable filtering by state #12
Open
Conversation
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
State filter, basic working model
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
…ale filters, hide irrelevant filters and keep only relevant ones.
Filter out irrelevant filters when drilling down or backing up for states and locales
Isotope Filters / Fix wonky sorting
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
… alternate templates, and allow some more or less direct SQL query access.
…arrays, allowing for ROWID queries. Google's sub-SQL dialect apparently can't handle sending ROWID through an IN operator?
shortcode enhancements
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
Signed-off-by: Erica <e@energy7.com>
…nctionality into a dedicated class for handling Sahana Feature objects.
…ns fail. Key-sort the row arrays so that they come in proper numerical order even if columns that get assigned indices later show up earlier.
…a WHERE clause from the front-end back into the data-source interface. I just want to guarantee that the matches parameter will work with any data source; I don't want to write an SQL expression parser for any non-SQL data source.
…for their own HTTP fetching.
… for Sahana JSONP.
…. We determine which we are using by doing some wack sniffing on the URL provided.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Right now this works but it is crude. All locales will display as filtering options, whether or not those locales are in the current state.