[WIP, DON'T MERGE] Replacing Typeahead, site-wide#5420
Open
[WIP, DON'T MERGE] Replacing Typeahead, site-wide#5420
Conversation
5 tasks
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.
Summary
Replacing Typeahead with Autocomplete
Required reviewers
Impacted areas of the application
Screenshots
Should be no visual changes
Related PRs
None
Known issues
Still working on MUR search, and need to test Legal and RAD lookups
How to test
There are a lot of places to test and a lot of ways, but they should generally all pass or fail the same way.
Generally, we want to make sure it
Environment variable
There's an environment variable (
FEC_USE_TYPEAHEAD) that will control whether the searches and lookups will use Typeahead or Autosuggest. To check which one you're getting, check developer tools:twitter-typeahead,tt-inputautoComplete_andautosuggestHow to set:
Truein your terminal orTrueinbase.pyorFEATURES['use_tt'] = Trueunderif FEC_CMS_ENVIRONMENT == ENVIRONMENTS['local']Falsein your terminal orFalseinbase.pyorFEATURES['use_tt'] = Falseunderif FEC_CMS_ENVIRONMENT == ENVIRONMENTS['local']Site header search on homepage
/data/receipts/individual-contributions/?contributor_name=[your term]/search/?type=candidates&type=committees&type=site&query=[your term]▪
Site header search on search page
Functionalityif the field builds and works correctly on the homepage, it'll be fine here▪
Site header search on any datatables page with filters (individual contributions)
Functionalityif the field builds and works correctly on the homepage, it'll be fine hereDesktop, keyboardif it works for /search, it'll work herePhone/tablet, touchif it works for /search, it'll work hereSearch page
/data/receipts/individual-contributions/?contributor_name=[your term]/search/?type=candidates&type=committees&type=site&query=[your term]▪
Datatables filters (individual contributions)
▪
RAD contact form
name="u_committee")▪
Audit search
▪
Desktop, keyboardthis functionality is the same across every Autosuggest filterPhone/tablet, touchthis functionality is the same across every Autosuggest filterMUR Search
▪
Desktop, keyboardthis functionality is the same across every Autosuggest filterPhone/tablet, touchthis functionality is the same across every Autosuggest filterBy the numbers (raising, spending)
▪
Desktop, keyboardthis functionality is the same across every Autosuggest filterPhone/tablet, touchthis functionality is the same across every Autosuggest filter