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

Refactor 0.3 #59

Merged
merged 37 commits into from
May 6, 2022
Merged

Refactor 0.3 #59

merged 37 commits into from
May 6, 2022

Conversation

floodfx
Copy link
Owner

@floodfx floodfx commented Apr 24, 2022

Basically a re-architecture, refactoring of LiveViewJS into multiple different packages primarily to support both NodeJS and Deno runtimes.

Package structure is:

  • <root> - "Core" LiveViewJS package that defines the main types, implement the LiveViewProtocol, and management of LiveViews for HTTP and Websockets. This is written in TS that works both on NodeJS and Deno.
  • packages/examples - numerous LiveViewJS examples show both simple and complex LiveViews which are usable in both NodeJS and Deno
  • packages/deno - Code that enables developers to use LiveViewJS in their Deno + Oak applications along with a working example Deno + Oak server which loads the LiveView examples from packages/example.
  • packages/express - Code that enables developers to use LiveViewJS in their NodeJS + ExpressJS applications along with a working example NodeJS + Express server which loads the LiveView examples from packages/example.

In addition, we cleaned up the type system, refactored a bunch of types, fixed bugs, written tests, and generally learned a lot! Also fixed #25, #30 , #36

floodfx added 30 commits April 3, 2022 07:47
…it; refactor express away from live view server
…_map.json, add README, and generally make project easy to grok
…rent lifecycle has sent a response to process
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

Successfully merging this pull request may close these issues.

Use "_target" hint on phx-change form events to inform params passed to handleEvent
1 participant