History

Anish Lakhwara f24e56159a feat: parse multiple commands basically at MVP now the react app can now add, complete and reactively filter tasks The filter command doesn't have a enter action, it should probably do something. maybe I do need the default to be select, instead of filter, and filter should _actually filter_. Syncing is next. I'll need to look at the vcln starter template to understand how they set up, and then maintain different databases for each user. What needs to be done is setting up rooms, and the backend such that everybody gets their own lil sql database, and the syncer can identify them. we don't really have any notion of security, which is uhhh, not great. After that we can look at some malleable features that lend themself to discoverability. ideally, I don't need to have a tutorial at all. reactivity needs to exist for almost every command. I want to save the command, to a dirty state sql table, and then restore it on load. that should cause all the elements to re-render the proposed change. this actually unlocks a thought for me: executing filters, sets them as a "context". a context makes up a view. reports are literally just saved contexts then. this allows the tanstack table to handle virtual ids for us! Then, for the malleable input, all we need some kind of triple scroll wheel that can be typed, for each of the three segments. ideally with desired autocomplete 🤔 i think i'm reimagining the CLI for the web almost!		2024-11-10 18:15:20 -08:00
..
public	init mast-react	2024-11-02 17:29:52 -07:00
src	feat: parse multiple commands	2024-11-10 18:15:20 -08:00
.gitignore	init mast-react	2024-11-02 17:29:52 -07:00
components.json	a little nicer looking, but i still don't really understand where to set	2024-11-06 22:21:58 -08:00
eslint.config.js	init mast-react	2024-11-02 17:29:52 -07:00
index.html	init mast-react	2024-11-02 17:29:52 -07:00
package-lock.json	init mast-react	2024-11-02 17:29:52 -07:00
package.json	init mast-react	2024-11-02 17:29:52 -07:00
postcss.config.js	init mast-react	2024-11-02 17:29:52 -07:00
README.md	init mast-react	2024-11-02 17:29:52 -07:00
tailwind.config.js	a little nicer looking, but i still don't really understand where to set	2024-11-06 22:21:58 -08:00
tsconfig.app.json	init mast-react	2024-11-02 17:29:52 -07:00
tsconfig.json	init mast-react	2024-11-02 17:29:52 -07:00
tsconfig.node.json	init mast-react	2024-11-02 17:29:52 -07:00
vite.config.ts	init mast-react	2024-11-02 17:29:52 -07:00

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

Configure the top-level parserOptions property like this:

export default tseslint.config({
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})

Replace tseslint.configs.recommended to tseslint.configs.recommendedTypeChecked or tseslint.configs.strictTypeChecked
Optionally add ...tseslint.configs.stylisticTypeChecked
Install eslint-plugin-react and update the config:

// eslint.config.js
import react from 'eslint-plugin-react'

export default tseslint.config({
  // Set the react version
  settings: { react: { version: '18.3' } },
  plugins: {
    // Add the react plugin
    react,
  },
  rules: {
    // other rules...
    // Enable its recommended rules
    ...react.configs.recommended.rules,
    ...react.configs['jsx-runtime'].rules,
  },
})