rbhicks / hashbump Goto Github PK

do a refetch in the bump handler

The ui and currentHashtag isn't getting updated (but the new hashtag is being created). Need to check to see if handleChange with no existing record is working.

clean up the formatting and lock down all the prop types

the divs end up overlapping instead of going to one on top of the other (it might be the float positioning)

The internal logic calculates “top hashtags this week” but the dispaly reads “top hashtags today”.

Pick one.

for third party use

strip all the parts of the starter kit that aren't needed

bumping should also be available from the icons in either of the top lists

It looks like the current implementation is fighting against "functional & composable", how apollo works, and conflating the idea of a field to query with (current hashtag name)...i.e., how apollo works, with the actual current hashtag object itself.

It seems that the best way to go might be to go back to storing just the name/partial name in redux and having the hashtag input and the bump button both query for the object and let apollo handle it.

if you bump a hashtag that in in the top count display, the count is only updated after a full page reset

repro:

1. on mobile enter non-existent hashtag
2. bump (to create)
3. delete characters until suggestions appear
4. retype hashtag

It doesn't show up in the suggestions until the page is refreshed.

(internal optimization for mobile in apollo?)

if a hashtag is the tops hashtags is tapped, populate the edit box with it

Are they stateless if the use redux and apollo?

If not, can they be made stateless with an autosuggest?

Are they organized properly to allow this?

visual only, i.e.: no buttons, but with a description (trending, all stars, etc)

If there's no bumps for the today count, the loading field hangs.

either make it sort of a joke or suppress it

the weird null behavior might be the same as what came up in bumpDisplay until it was fixed

There are various methods to get solr to rebuild the index. There might be one when a new record is created (almost surely won't scale). It should also be possible to trigger the rebuild on demand.