Katalina
3291f9aacc
* miniflare init * feat(api): add tests * chore: more tests, almost 100% * add sessions/state spec * add majority of routes and datapaths, start on interactions * nevermind, no interactions * nevermind x2, tweetnacl is bad but SubtleCrypto has what we need apparently * simplify interactions verify * add brute force interactions tests * every primary path API route is refactored! * automatically import from legacy, or die trying. * check that we only fetch legacy once, ever * remove old-src, same some historic pieces * remove interactions & worker-utils package, update misc/types * update some packages we don't need specific pinning for anymore * update web references to API routes since they all changed * fix all linting issues, upgrade most packages * fix tests, divorce enzyme where-ever possible * update web, fix integration issues * pre-build api * fix tests * move api pretest to api package.json instead of CI * remove interactions from terraform, fix deploy side configs * update to tf 1.1.4 * prevent double writes to worker in GCS, port to newer GCP auth workflow * fix api.tf var refs, upgrade node action * change to curl-based script upload for worker script due to terraform provider limitations * oh no, cloudflare freaked out :( |
||
|---|---|---|
| .. | ||
| .storybook | ||
| atoms | ||
| fixtures | ||
| hack | ||
| molecules | ||
| organisms | ||
| templates | ||
| Intro.stories.mdx | ||
| jest.config.js | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.test.json | ||
Roleypoly Design System
Codename: rapid
The Roleypoly Design System (rapid) is an atomic design system to help rapidly and consistently build Roleypoly and related services. The color system in use is deliberately simple, and should be adhered to.
Developing
Please follow hermeticity considerations.
This package cannot reference RPC types, as they do not exist in the outside world. Storybook is the core component of this, and Storybook doesn't know how to find RPC types at CI build time, as Bazel is also not present. If you are worried about RPC types being compatible, please write a unit test and include the RPC types then.
You need:
node(lts or later)yarn(v1.x)
Run:
yarn start:design-systemto get started.
Need to make a new component?
yarn create-component <atomic-type> <name>- This will create the skeleton files needed for a component.
- See below for atomic types.
Atomic Design 101
Components are split into the following categories:
- atoms
- smallest possible parts.
- typically individual pieces, such as branding, layout macros, and style-wrapped native elements.
- molecules
- groups of atoms
- typically these make up sections of major UI parts
- organisms
- groups of molecules
- typically these are major UI parts
- templates
- groups of organisms
- typically a full page, without data.
- pages
- not covered by rapid
- routes data into templates.
This sort of layout works extremely well with Next.js, the UI toolkit within Roleypoly. You should also be able to develop most parts, up until pages, directly within Storybook.