The warning region does not grow at the edges This makes it harder for
the user to get into an odd state. It might be better to have let the
user expand the second region at the trailing edge. I'm not sure, and
that's harder to implement.
The editor should handle its own rendering. By including a key that
changes as the users changes tabs forces the editor to re-render. This
gets triggered as the user types, resetting the cursor to the start of
the editor.
Now the key only changes if the theme changes.
Generates models to handle multiple groups of code (html, js or css) and
tracks the editor state as user moves between tabs. The current model
is connected to the redux store via a key associated with the file in
the editor.
* Add meta.json for spreadsheet
* Add spreadsheet files
* Close code tags for tests in 2 files
* Add solution section
* Add index file
* Add javascript-spreadsheet to stringifier
* Move index to step
* Rename steps in meta.json
* Rename step numbers in files
* Add index file to proper location
* Remove inappropriate files from spreadsheet dir
* Fix typo in first step
* Fix test sections
* Rename files to correct step
* Fix broken tests
* Add newline between sections
* Change challengeType from 1 to 0
* Add missng ) in step-079.md
* test -> tests in step-079
* Simplify test in step-103
* Fix step-137 test
* Remove last step
* Added solutions and adjusted some tests
* Fix some challenges
* Remove wrong spaces
* Fix more tests
* Add missing semicolon
* Fix more tests
* Fix type: lastttwo
* Fix all remaining tests
* Added new section
Added new section: Dealing with (mental) health inquires. This was done on request from Quincy.
* Update docs/flight-manuals/moderator-handbook.md
Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
Co-authored-by: Nicholas Carrigan <nhcarrigan@gmail.com>
* Add scripts for Cypress to run on other browsers
* Run Cypress on different browsers in workflow
* Install Brave and run it in Cypress
* Run Cypress on only CHrome and FIrefox
* Revert Cypress plugin
