Swizec Teller - a geek with a hatswizec.com

    Fast, searchable dropdown inputs with React

    Input fields that are limited to one of 6,000 possible values… That’s a usability nightmare, right? ?

    Dump it in a dropdown, and you overwhelm your users. How many even know vanilla dropdowns support search? And besides, you can't style those. Your designer will throw a shit fit. Default browser crap in his beautiful design? No, no, that won't do.

    Looks vanilla, works vanilla. First open is slow, but search is fast if you know it exists. If you don't, you're screwed.

    You could give users an input field and validate against the list of possible entries… no way that's going to be a nightmare, eh? Is it stanford, Stanford, stanford university, Stanford university, or Stanford University? Some people will enter stnraofd.

    No, no, the answer is both. You need an input field and a dropdown. Input filters dropdown, dropdown guides users.

    Step 1: react-select

    Jed Watson's react-select library gives you input fields with dropdowns. Users can use the input field or use the dropdown.

    Implementation looks like this:

    import Select from 'react-select';
    import 'react-select/dist/react-select.css';
    const options = [
    // ...
    { value: 'Stanford University', label: 'Stanford' },
    // ...
    ];
    const field = ({ options }) => (
    <select name="university" value="one" options={options} onchange="{val" ==""> console.log(val)}
    />
    );
    The <Select> component does everything: input field, styled non-vanilla dropdown, mouse interaction, keyboard shortcuts, filtering. The only gotcha is that options have to be an array of { value, label } objects. Even if both value and label are the same, I tried.A few seconds to render the dropdown. A few seconds to filter. The browser's UI thread blocked, and you can't even see what you're typing.5,258 entries is a lot of entries ?Step 2: react-virtualized-selectBrian Vaughn's react-virtualized-select solves the first problem – opening the dropdown. It's a higher order component that does a thing and then your thing works better.I think it implements paging and hides it behind scroll events. Only a few elements render at a time, and everyone's life is better.Here's how you use it:
    import Select from 'react-virtualized-select';
    import 'react-select/dist/react-select.css';
    import 'react-virtualized/styles.css'
    import 'react-virtualized-select/styles.css'const options = [
    // ...
    { value: 'Stanford University', label: 'Stanford' },
    // ...
    ];const field = ({ options }) => (
    </select> console.log(val)}
    />
    );

    We changed the import Select from to use react-virtualized-select and… that's all. ?

    It opens quickly, and I was typing that whole time that nothing was happening. Browser's UI thread still blocking.

    Step 3: react-select-fast-filter-options

    Brian Vaughn's react-select-fast-filter-options is practically too long to mention in a tweet, and it solves the second problem: fast search.

    It builds an index of your options and uses advanced computer sciencey algorithms discovered some time in the 60's, probably. We rarely have enough data to worry about actual computer science on the front end, but sometimes we do.

    Here's how you use it:

    import Select from 'react-virtualized-select';
    import createFilterOptions from 'react-select-fast-filter-options';
    import 'react-select/dist/react-select.css';
    import 'react-virtualized/styles.css'
    import 'react-virtualized-select/styles.css'
    const options = [
    // ...
    { value: 'Stanford University', label: 'Stanford' },
    // ...
    ];
    const filterOptions = createFilterOptions({ options });
    const field = ({ options }) => (
    <select name="university" value="one" options={options} filteroptions={filterOptions} onchange="{val" ==""> console.log(val)}
    />
    );
    We added a filterOptions prop to Select, which specifies a custom filter implementation, and we used createFilterOptions to instantiate that implementation. No need to worry about how it actually works because It Just Works™.Looks good, works good. Faster even than the vanilla browser implementation ?The only gotcha is that you have to pass the same options to both Select and createFilterOptions. Dynamically generating { value, label } objects from an array won't work.The good news is that the memoization MobX does for @computed values is good enough, so you can do something like this:
    class FormData {
    @observable universities = ['Stanford', 'UVA', ...];
    @computed get options() {
    return this.universities.map(name => ({ value: name, label: name }));
    }
    @computed get filterOptions() {
    const options = this.options;
    return createFilterOptions({ options });
    }
    }
    I don't know if it would work with Redux. As long as you're careful about the reference thing, you should be fine.But is it a good idea?Yes. Use this approach for all select fields. Even the small ones! There's no harm, and it's faster. Winning.</select>

    Did you enjoy this article?

    Published on November 16th, 2016 in Front End, react, Technical,

    Learned something new?
    Read more Software Engineering Lessons from Production

    I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.

    Subscribe below 👇

    Software Engineering Lessons from Production

    Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.

    "Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"

    ~ Ashish Kumar

    Join 15,883+ engineers learning lessons from my "raw and honest from the heart" emails.

    ⭐️⭐️⭐️⭐️✨
    4.5 stars average rating

    Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.

    Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.

    Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.

    Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev

    Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization

    Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections

    Want to brush up on modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created by Swizec with ❤️