crispinb / chrello Goto Github PK

A new approach:

• htmx-based 'front end'
• with a service worker redirecting REST requests to:
• an in-browser WASM intermediary, which:
  • converts these to JSON requests, submitted to the Checkvist API
  • converts the responses to HTML partials, returned to the f/e
  • caches those responses to provide some offline capability

We'll get a token and choose list from an env var for now
Top level tasks are columns, child tasks are cards
No interaction yet

• lay out board components, displaying canned data
• replace canned data with data from API
• lay out errors in a page or modal

How well does it work with different resolutions OOB?

Tauri supports both mocking the back end & webdriver tests.

Currently inclined towards the latter as e/e tests as I see b/e mocking as a bit pointless, and mostly of use when exploring a new feature which is best done interactively anyway.