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

Both client and server side ? #1

Open
gedw99 opened this issue Oct 5, 2024 · 2 comments
Open

Both client and server side ? #1

gedw99 opened this issue Oct 5, 2024 · 2 comments

Comments

@gedw99
Copy link

gedw99 commented Oct 5, 2024

Hey @godsarmy

mega cool .

I have been meaning to do this and you have for me and others .

what do you think about leveraging both SSR and CSR ? Isomorphic is the fancy pants word for this :)

the CSR would use json from the server .

once you go down this rabbit hole it gets depleting to do mutations optimistically on the client ?

@godsarmy
Copy link
Owner

godsarmy commented Oct 5, 2024

Hi @gedw99

I believe most developers use both SSR and CSR together when they apply HTMX to their website (e.g. if you want to embed the powerful table library tabulator). In most of HTMX projects, CSR would increase the project complexity and is not recommended except:

  1. The lib is much easier to use in CSR (tabulator, e.g)
  2. You are not allowed to change the Server API. (my project falls into this categrory).

@gedw99
Copy link
Author

gedw99 commented Oct 6, 2024

Hey

https://github.com/gedw99/goPocJsonSchemaForm Is runtime . So you can change the json schema and the HTML changes .

So I plan to try out using your repo with my json schema approach .

that tabulator looks like a great base for the “ Master” page as described in my repo .

https://github.com/olifolkerd/tabulator Could be driven by numjucks , which is driven by the json schema. Just brain storming this :)

Have a look :) it’s easy to run ..

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