arktypeio / arktype Goto Github PK

security review

• Investigate how analytics API works for storing keys security
  -- remove app secret from redo-server\

First steps:

1. Take ChipInput out of app (currently in learner page) and move it to components

2. Make a new ChipInput component that looks like our Button component in that it:

• imports the material-ui ChipInput component and props

• wraps them up and can add custom props if needed

3. Rely on the @re-do/components chip input from app and delete material-ui-chip-input dependency from app

1. SuggestionsCard should get real data as part of this task.
2. Users can view recorded test cases and other saved data like groups of elements/actions, test suites etc. in both search and hierarchical formats

make an abstraction for sign up and sign in pages
split up learner page to be more manageable -- use chipinput as form, rip stuff out to make learner leaner

Need to get cross-platform build output for Redo. Should be able to do so using this tool:

https://www.electron.build

The documentation looks very detailed although you might find it hard to understand most of what's going on. Would recommend just trying to glean as much as you can and try to get one small thing running at a time. If you are making lots of changes to different files, something is probably going wrong :)

To start, let's shoot for:

1. Being able to run "npm run pack" and get the following build output variants (see documentation):
   .dmg, .deb, .nsis, .tar.gz

Once we can do this, we'll want to be able to run "npm run publish" and get those files into AWS (Sarthak is working on getting AWS set up today, so you'll need to coordinate with him). Looks like there's info about that process here:

https://www.electron.build/configuration/publish

Any progress you can make would be super helpful, may involve some head banging though 🍀

1. 1/2 day Github continuous integration process set up

2. figure out versioning scheme for packages

3. add analytics to app with segment

RespondTo also needs a general refactor including:

Update RespondTo using React.cloneElement for children

Make child components more easily configurable

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
in Unknown (created by SignIn)
in FormContext
in Unknown (created by SignIn)
in div (created by ForwardRef(Paper))
in ForwardRef(Paper) (created by WithStyles(ForwardRef(Paper)))
in WithStyles(ForwardRef(Paper)) (created by ForwardRef(Card))
in ForwardRef(Card) (created by WithStyles(ForwardRef(Card)))
in WithStyles(ForwardRef(Card))
in Unknown
in Unknown (created by SignIn)
in div (created by ForwardRef(Grid))
in ForwardRef(Grid) (created by WithStyles(ForwardRef(Grid)))
in WithStyles(ForwardRef(Grid))
in Unknown
in Unknown (created by SignIn)
in SignIn

Throughout our app it's a common pattern to import components from material-ui and then wrap them in our own customized versions of those components with some defaults assumed. To make it clear at which layers we're looking at MUI components and when it's our own custom components (often by the same name), I'd like to standardize on importing material-ui components with a prefix of Mui. E.g.:

import {Button as MuiButton} from "@material-ui/core"

This should make it easier to debug code in the future and to help us tell at a glance which components are ours.

Should be able to run basic redo test command from CLI and get jest-like pass/fail results or from the UI and get some basic version of the same.

(e.g. BrowserEventInput in TestInput, TagInput in TestInput etc.)

See pkgs/redo-model/test.ts