Downshift: Name change

[souporserious]

Pertaining to https://github.com/kentcdodds/react-autocompletely/issues/1 I personally think it would be beneficial to choose a name that promotes this library for multiple use cases. I think by naming it anything with autocomplete could paint the library into a corner. I'd love to see Dropdown, Select and other cool components made with this. The hard part is I have no idea what a new name could be 💩

Some quick ones:

• rechoose - react + choose
• reelect - react + elect (maybe just elect by itself?)
• repick - react + pick
• picknic - 🤷‍♂️

[kentcdodds]

So, honestly, what's the difference between all of these components? I feel like their names are all a little interchangeable right?

[souporserious]

I'm not sure what you mean? I'm proposing a library name change, so it would be something like:

import { Manager, Input, Menu, Item } from 'react-choose'

function Select({ items }) {
  return (
    <Manager>
      <Input/>
      <Menu>
        {items.map(item => <Item {...item}/>)}
      </Menu>
    </Manager>
  )
}

Maybe just changing the component names would be enough? I just like the idea of it for other use cases and feel it would be weird to see an Autocomplete component powering a Dropdown.

[kentcdodds]

Yeah, my question is, from a design perspective, what's the difference between a dropdown, select, and autocomplete component? Aren't they all basically the same thing?

[joao-alberto]

Aren't they all basically the same thing?

Dropdown not, but select and autocomplete basically yes, because dropdown not necessarily handle state, it can be just a menu.

[rouzbeh84]

Interesting idea here. For dropdown/select I've used this http://jedwatson.github.io/react-select/ before and it worked quit nicely in a 'live' update scenario (I.e. Enter values in one select and upon change focus, subsequent select on same view gets just added values to a multi select from) fairly efficiently.

[kentcdodds]

I think that the lines are totally blurred in all of these components. You'll notice that the semantic-ui docs refer to their similar component as a dropdown.

I think that I'm going to stick with react-autocompletely. Maybe you could have convinced me to change it before I selected an emoji for the project, but now I just can't go back 🔮

Thanks!

[souporserious]

Haha no worries! I'm totally fine either way, this lib is great so far 🙌

[kentcdodds]

Ok, clearly the name is confusing people.

I'm happy to rename this project, but it's gotta be good.

Why don't we come up with several suggestions, then I can make a twitter poll and see what folks think...

[souporserious]

😇 I'll give you selectly if you want it, since it's similar to the current name 😁

[kentcdodds]

We can make that an option. Though I'd like react in the name honestly. I don't expect that this'll ever work without (P)react...

[souporserious]

Sounds good 👍 react-selectly should be available. I'll try to think of some other names 🤔

[bernard-lin]

react-optionally 😂

[kentcdodds]

Ok, here's the tweet :smile:

[kentcdodds]

Because react-autocompletely can support such a wide variety of use cases, @markdalgleish suggested that we come up with a catching but totally meaningless name.

I like the idea! What do you think? Bonus points if it's in reference to something from ancient times (like greek mythology or Medieval times or something).

[kentcdodds]

Sometimes it might help to think of a logo/emoji first and then come up with a cool name. Here are some emoji that I think would be cool:

⚡️ 🔥 🔮 💫 ✨ 💥 🕵️‍♀️ 🔎 🌪

[bernard-lin]

I really like the Sherlock one...but probably because I really love the stories 😅

[kentcdodds]

Oh, what if we use a character from "Mistborn" (I'm reading it right now):

Mistborn are Allomancers who are able to gain power from all Allomantic metals, and are some of the most powerful characters in the Mistborn series.

Basically, Mistborn are rare. More commonly you'll find Mistings. Mistings have one of 8 available powers, but Mistborn have all 8 powers. So the idea of flexibility is strong here.

So we could use Kelsier (not taken). Though... we might run into trademark issues 🤔 #leftpad

As for an emoji/logo.... 💥 seems appropriate 🤔

Maybe not 🙃

[kentcdodds]

Azula might be cool to go with 🔥

[gricard]

react-selectively
react-positively
react-specifically
react-picky
react-choosey
react-pickle
react-pickly

[rouzbeh84]

that could be cool. i was thinking along the lines of animals like an owl 🦉 for all knowing wise, elephant 🐘 for it's memory/recollection, or even a golden-retriever 🐕 for it's....well, retrieving haha. might be a bit of a stretch though.

maybe just react-zoltan like the fortune teller or react-acadabra with a 🎩 for a magician 😝

[mateo-io]

reactive-react

[souporserious]

react-choo 🚂
react-gather 👐
react-harvest 🌾
react-retriever 🐕 (credit to @rouzbeh84 from above, writing it out makes it sound so cool! 😎)
react-kadabra 🔮 (inspired by @rouzbeh84 again, and pokémon!)

[kentcdodds]

I'm liking:

• react-kadabra 🔮
• react-retriever 🐕

But honestly I'm starting to think that react-autocompletely is pretty good and we should just stick with it. I dunno... It's already gotten a fair amount of traction.

[souporserious]

I vote for react-kadabra. I like that you can use the same emoji with it and since the library is still fairly new I think the name change would be fine and hopefully help mitigate any confusion on it being only an autocomplete component. Plus, with a name like kadabra, we could make a reallllllly cool demo site since it has a sort of theme to it 😁

[kentcdodds]

Plus, with a name like kadabra, we could make a reallllllly cool demo site since it has a sort of theme to it 😁

Alright, if you commit to making a cool demo site then consider it done.

[souporserious]

I'm soooo down 😍

[kentcdodds]

Nice!

[kentcdodds]

~/Developer/react-kadabra (master)
💪  $ npm publish --tag beta
+ [email protected]

[kentcdodds]

It'll take a little time for travis to update but hopefully it'll happen soon

[souporserious]

😱 🎉 yay! I'm leaving for vacation for two weeks soon, but when I get back I'm on it 💪

[rouzbeh84]

HOORAY! 👏🏽 🎉

@souporserious holler when you get back, i'll def try to help you out on the demo site if you'd like 🙏🏽

[kentcdodds]

I'll try to setup Netlify on this repo so we have an easy deployment story :smile:

[kentcdodds]

This is a good point: https://twitter.com/AntJanus/status/893116305431068673

We should probably avoid tying ourselves to the pokemon for this reason...

[kentcdodds]

And with that I'm honestly thinking that react-retriever 🐕 may be better... Yikes, all this naming stuff is giving me a headache.

[souporserious]

Oh dang that's a good point 😞 I always liked react-retriever as well. I don't know which is harder, a good API or naming something 💩

[kentcdodds]

Problem with react-retriever is it's not entirely easy to spell. Not a really common word people use...

Back to the drawing board....

[souporserious]

Orrr react-cadabra? Playing off of Abracadabra and not pokemon so there aren't any lawsuits and the emoji makes more sense 😁

[rouzbeh84]

react-resilience cause who knows what people are gonna put in your form inputs ;). Jk haha

I like both of the resurgent finalists. FYI I only rethink in re-insert-words now 🤣😂

[alexkrolick]

I spelled "kadabra" wrong like 3 times (trying different variants of abacadabra) whilw Googling after seeing it on Twitter and got really irrelevant results. Maybe as it gets more popular it will rank higher but right now... Not so great.

OTH I do like the Ruby convention of using somewhat fanciful or uncommon names for libraries to avoid giving the appearance of there being an official or "blessed" library in hot namespaces where there could be multiple competing projects. NPM, and react in general, is terrible in this regard (looking at you react-router!).

[kentcdodds]

I definitely want to keep this react specific as it is a react library, so having react in the name is important IMO (despite the drawbacks you mention).

I spelled "kadabra" wrong like 3 times

Yeah, that's unfortunate... Let's go with something easy to spell.

[rossipedia]

react-completionist
react-volunteer
react-ucompleteme (please don't)

[alexkrolick]

react specific as it is a react library

The react part is fine and makes sense, it's "well I'm the first library here so I get the most obvious name" part that isn't great. I.e., react-select, react-router are one of many.

~Is there always an input box? If so, "react-typeahead-toolkit" is probably sufficiently specific to avoid future naming conflicts, without using nonsense words.~ Nope.

[souporserious]

That's part of the issue 😕 there doesn't always need to be an input. It can be used to make a simple dropdown with keyboard navigation as well as other components.

[tkh44]

downshift

[kentcdodds]

I like that a lot actually @tkh44!

Now for a emoji... The first thing that comes to mind is 🏎 which is totally awesome 🕶

Should it be react-downshift or just downshift?

Honestly... Someone could wrap this lib up in preact-habitat by @zouhir and they could use it in any framework. It'd be pretty slick (and small) actually!

So I'm thinking simply downshift...

[tkh44]

I would just use the word without the react prefix.

[bernard-lin]

second that!

[kentcdodds]

@souporserious what do you think?

[souporserious]

:shipit: 🏎 🎉

[souporserious]

I like single names as well :) I don't think it necessarily needs react in the name. Think of all of the jQuery plugins that came out that didn't prefix jQuery.

[souporserious]

You cool to wait to change until the multiple stuff is done? 😁

[kentcdodds]

Sure, if you're working on it now :wink:

[kentcdodds]

So here's what I'm thinking about for a logo:

That emoji is coming from emojione (which is where I got the glamorous logo from)

But someone suggested I use the one from twemoji:

I like this because it means that the logo will look the same on the project as it does on twitter... But I kinda like the red one more...

Give an emoji response on the comment to indicate which you like better:

• Emojione (red car): :tada:
• twemoji (orange/blue car): 😄

[kentcdodds]

Another thing to consider is I don't have an SVG for the one from emojione so we'd have to make that ourselves....

[souporserious]

Coming from a design standpoint, I like the red car better 😁

[kentcdodds]

Ok! Rename is done and I added a simple png logo. Hoping to get a nice SVG soon!

[kentcdodds]

Oh snap. My friend @strack just sent me this as an SVG! :tada:

I'll update the logo on the README with this. Thanks tons Isaac!

[josephrexme]

Oops I guess I'm late. I did this https://gist.github.com/josephrexme/d35258ac2bc0ef5038795f2e8eee8860

[kentcdodds]

Ah, but 2 minutes! Thanks for working on it! I've already updated it with what Isaac sent me. I think I'll leave it as is. I really appreciate what you've done though, thank you :)

If you still want to help out, I'd love to have a help codesandbox (like the one for glamorous). If you'd like to make that, I'd love it :smile:

[pqr]

react-pqr - simple, short, alphabet for everything