zachlysobey / chat-prototype

It's me, Zach!

Usage

npm

npx zachlysobey

GitHub Package Registry

Assuming you have the GitHub registry set up, you can use via npx:

npx @zachlysobey/card

Not including how to use it globally because I'm not sure why you'd want this as a global command. That'd be creepy.

chat-prototype's Issues

Clean up / refactor redux usage

I left this stuff kind of a mess and never really considered the best approach. Its far enough along now that I should revisit this before adding any more features. At the very least I should reconsider the actions names and reducer set up. But I expect with some thought I'd come up with better abstractions for this stuff in general. And maybe redux is not the right tool for the job anyway.

Add CI pipeline

This would usually be the first thing I set up, along with some tests. But for the sake of expediency...

Consider top level scripts for installing/starting/building

This would make it unnecessary to do a lot of cd-ing around which is a pain

Welcome modal is not keyboard accessible (does not submit with return)

This is actually kind of infuriating and I couldn't resolve in 2 minutes so I gave up. This is a necessary enhancement.

Avatars with Gravatar

I think this would probably be pretty easy, and class this thing up a bit

Database persistence

This would allow for chat persistence even after the chat server shuts down.

host this somewhere?

been meaning to check out netlify. Or AWS/Azure/GCP are always a viable choice.

Dockerized build

It'd be pretty trivial to drop this whole thing into a docker image.

Refactor Go code

This was my first go-code I've written. I spent a few minutes trying to refactor, but was stumbling around, and decided to bail on the effort. Its small enough that a few chunky methods and ugly code is acceptable to me, but this could really use some attention?

Support multiple browser sessions in a single chat

Currently each browser gets its own, isolated chat per websocket connection. This makes the chat kind of lame.

Add github link

Since this is open source, might as well link back to GitHub

Auto-reload for Go-code developement (a la nodemon)

Tabbing over to the console and manually stopping/restarting the server sucks. The earlier I get a system for automating this the more time I'll save overall...

Some sort of user authentication

Add some special responses

Using the same general mechanism as I did for the "<connected>" messages, I can add special responses to the go server. Like... If you send "what time is it" the ChatBot can respond with the time, etc...

add prettier (and lint?) with precommit hook

I didn't spend much time on code-style stuff, as it should be automated away. I should do this before going much further.

Ensure tree-shaking is working fine and bundle sizes are managable

Previously, I've had to do some tricks to get tree-shaking working with Ramda, so its likely there are issues that can be addressed for smaller bundle sizes.

If this was a real project, I should set a performance budget and some fitness tests.

Consider the design

This design was pretty emergent and I did not give it any real thought. Before going too much further with the client it makes sense perhaps to sit down and think about the design -- perhaps comparing it to existing projects, and generating some new issues for incremental steps to improve it.

Image and URL detection

It's be pretty easy to detect urls, and wrap 'em in <a> and/or <img> tags..

Add a message counter

Per the original specifications:

• User can type any number of other messages that append to the window chat room and a message counter at top increments up as each message is added live