* Create a drop down menu
Co-authored-by: ahmad abdolsaheb <ahmad.abdolsaheb@gmail.com>
Co-authored-by: moshe vilner <shootermv@gmail.com>
hopefully sort the tests
hopefully sort the test this time
this time? I hope
test compound component
I give up
This reverts commit d88c6783cccf811c3c5dced0ab980adff0172669.
headless doesn't pass onclick to its buttons children
add the logical statment back
revert the removing the ability to click
sort the tests
fix a typo
* sort the tests
* rename to menu item
* let dropdown trigger accept children
* include dropdown and menu items in the exports
* polish the logic around setting the dropup style
* add tests
* fix: typo DropDown to Dropdown
* sort the styles
* sort the type and add bsStyle to dropdownToggle
* fix: types in button and menu items
* align text to center
* remove the bsstyle and block logic from dropdown
Co-authored-by: ahmad abdolsaheb <ahmad.abdolsaheb@gmail.com>
* add w-full to sort default button not taking all width
* move the styling dependecy away from dev
Co-authored-by: ahmad abdolsaheb <ahmad.abdolsaheb@gmail.com>
* stop the mutation
Co-authored-by: sembauke <semboot699@gmail.com>
* remove the extra story
---------
Co-authored-by: Sboonny <muhammedelruby@gmail.com>
Co-authored-by: Sboonny <muhammed@freecodecamp.org>
Co-authored-by: ahmad abdolsaheb <ahmad.abdolsaheb@gmail.com>
Co-authored-by: sembauke <semboot699@gmail.com>
* chore(deps): update jest monorepo to v29
* chore: install jest-environment-jsdom
* chore: update snapshots
* fix: update config to transform nanoid+uuid
* chore: update babel's node target
This does not seem strictly necessary, but is probably for the best.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* feat: npm -> pnpm
This resolves the issues with the gatsby client (gatsby-plugin-pnpm
deals with the fact that gatsby is relying on its own dependencies
being de-duped)
and challenge-editor (which doesn't seem to want to automatically install
codemirror and needed its own eslint config)
* fix: correct mocha path for curriculum tests
* fix: use select workspace with -F not -w
* fix: reorganise packages and restrict hoisting
pnpm works best if the workspaces keep their own dependencies, since
dependencies are not flattened and then what node resolves from a
require is predictable.
@types seem to be a special case and more care is required to prevent
them getting smushed together in the root (hence the .npmrc)
* fix: add types for tools + root
* fix: decouple challenge-auditor from client
* fix: add ui-components types
* fix(client): use the latest types for react 16
* fix: prettify
* fix: prettierignore pnpm-lock
* fix: relax hoisting
Turns out pnpm works just fine with types. I don't know what was going
wrong before, but there are no-longer any type conflicts.
* fix: add @redux-saga/core to fix eslint issue
It seems to only be redux-saga that import/named can't cope with, so it
is probably okay to work around this one.
* chore: add chai to tools/scripts/build
* fix: add store to root for cypress
* fix: allow cypress to download binaries
If we want to keep preventing cypress from downloading binaries, we can
figure out a workaround, but I'm allowing it to ease the transition to
pnpm.
My guess about why this is happening is that npm triggers Cypress's
postinstall script, but pnpm does not (because pnpm install only
installs if necessary, perferring to link)
* chore: re-enable pre/post scripts
* fix: update build scripts for client
Co-authored-by: Shaun Hamilton <shauhami020@gmail.com>
* chore: update engines to use pnpm
* fix: enable choice of (super)block for tests
Only 'nix machines for now.
* chore: pin pnpm to version 7
* chore: remove last npms
Except web + curriculum-server. I'll update them when I start work on
them again.
* fix: lockfile check to catch any package-locks
* fix(action): install pnpm for upcoming tests
* chore: add nodemon to new api
Co-authored-by: Shaun Hamilton <shauhami020@gmail.com>
