Hello @kodaman2,
Yes you're right, I think it could be nice to have a "refresh" button.

I'll see what I can come up for this issue.

Maybe just use this package?

I've tried it and it seems to work quite nicely. Maybe this is already good enough for now and something to work with?

I'll take a look at it tonight. Looks like is heading in the right direction. 😀 I still think the reloading needs to be handled another way like maybe Note.js new state property gistsLoaded, and a refresh button tied to the load action and/or a shortcut such as cmd/ctrl + r.

You give it a go then. Didn't want to steal this issue from you! :(

@jodli You're good, I'll try to submit a commit to your PR and that way is both our idea. 👍😁

Ok, now that I am done with the ghe auth PR, I can get back to this one. It might take me a little longer but cache or avoiding full notes reload will be implemented no doubt : )

After looking at the way the notes are loaded, it appears after each action (delete, edit, create), we fired up loadNotes which reloads all the notes each time.

What I am thinking is that after each edit, I'm going to update just each NoteCard without refreshing NotesList. And after create, or delete reactively update NotesList component without all the overhead of all the http gists requests. Of course we'll have to check github if any gists are added so gists.list() has parameter since: YYYY-MM-DDTHH:MM:SSZ which returns gists only since that date, and then those new gists can be added to the list of notes object. We'll that's the theory anyways, always easier on paper. Open to any ideas.