Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap #155

Open
wkhalif opened this issue Aug 31, 2023 · 2 comments
Open

Roadmap #155

wkhalif opened this issue Aug 31, 2023 · 2 comments

Comments

@wkhalif
Copy link

wkhalif commented Aug 31, 2023

This looks very promising. any roadmap planned ??

Thanks

@floodfx
Copy link
Owner

floodfx commented Aug 31, 2023

What would you like to see in a roadmap? What features are you interested in seeing implemented?

@wkhalif
Copy link
Author

wkhalif commented Sep 1, 2023

Well, i think it's still in the early stages so it's normal to have some issues. i run into a couple of ones.

  1. TS doesn't seem to recognize the socket repeat function socket
  2. The repeat function didn't really work as intended if we passed 1000 Millis the updates didn't happen every second, it happened like randomly
  3. I used setInterval to make the updates work instead of using socket.repeat. when i reload the page the server crashes with the following error
build\index.js:47400
    this.handleMsg([null, null, this.#ctx.joinId, "info", info]);
  1. Using the socket repeat and sendInfo function causes the page to reload every time it sends a tick which i found weird
  2. Some part of the hmtl i used is calculated in the render function and concatenated before the return. the page fails to interpret that part as HTML it is seen as a string

Features:
1, i think it will be very problematic to have the content of a huge page inserted in a return html`` statement so a support of templating would be better
2. it will also be great if we could compose LiveView's, something similar to React components or other approaches
3. to make automated updates from the server if we can have an approach like state management. when the state is invalidated it should automatically re-render the view
4. I think the use of sockets should be transparent. it will be better if most of the work appears like you're developing a client-side application and the framework will do the heavy lifting of the communication

Well am still experimenting with the library so I don't know if my suggestions are relevant or no, but I find the ideas behind it are great. I will be happy to contribute

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants