Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Actionable Updates

Kavika
-- Write out + send Zac requirements for API generation crate
-- Code review/fix Alex L's branch
-- Look into questions framework local code missing? Otherwise finish it (or maybe it's finished idk?)

Alexander Lai
-- chill / wait for the code review

Fritz
-- containerise things and setup docker
-- setup testing for handlers

Skye
-- push code for/finish answers framework

Alex M
-- idk lol i forgot what you need to do.. pls remind me

Yunshu
-- ensure all your final code is pushed + chill/wait for code review
-- do frontend tasks

Hellen
-- ensure all your final code is pushed + open a pull-request
-- do frontend tasks

Zac
-- look out for Kavika's requirements -> find/discuss the right solution

Josh
-- Merge in pull req -- sponsor logos
-- Cry over frontend refactoring
-- send Yunshu and Hellen frontend stuff

Agenda

announcements

cross-port bonding – wk6

update on code review [Kavika/Alex M/Alex L?]

frontend tasks

  1. User guide:

    1. we want to make a user guide on the website to:

      1. help people learn how to use CHAOS

      2. more clearly define what frontend features we need hahahahahaaaaa

    2. Tasks:

      1. Need to look into some sort of solution for this. Would something that renders mdx (or just markdown) be good? Don’t spend too long deciding, just do a lil bit of research and choose one. It should be easy to change later if needed (unlikely anyways).

        1. Docusaurus? → rendering mdx (mdx = markdown with extra features)

        2. Contentlayer

        3. Starlight

      2. Add the solution and make a basic guide on how users can create a campaign as a sample

      3. let’s use the route /guide for this

      4. Make a pull request

  2. Embedding OpenAPI spec on a webpage

    1. Create a page on the route /docs that displays the OpenAPI spec using the api .yaml file

    2. Make a PR

  3. Add typechecking + linting + formatting to the CI

    1. We want the frontend code to lint (ESLint) + typecheck (TypeScript) + be formatted (prettier)

    2. Tasks:

      1. add a github action in the .github/workflows folder that runs the three things (you will have to google the commands to run tsc, eslint and prettier in the CI)

      2. Make a pull request (the frontend build should fail this right now)

Actionables

  • No labels