* Revive this concept for 2023
(cherry picked from commit b3939d8426)
# Conflicts:
# pipeline/source_assets/scss/dark_screen.scss
* Update app.json
* Updates to all three layouts
* Add basic markdown support site wide
* Improved MD support.
Add some styling for images in MD
Add support for the bastardisation of the MD html for RML.
* Add processing for <ul> in RML
* Add OL processing to RML
* Fix a bug with squares appearing around the last page number
* Remove rml formatting in event_detail
* Improve handling of code blocks in RML
* Add MD to rigboard
Reduce MD title sizes as they were offensively large
* Add parsing of markdown when editing event items
* Improved list handling in RML
* Add tests for markdown support.
Focuses mainly on RML as that's where it will break
* Add indications of where MD support is enabled as per comment by @samozzy in #178.
Isn't quite a full description, but for the most part this should be enough for the people who know how to use it see where they can use it.
* Add failing test for markdown processing none
* Fix for failing test in e0d56e
* Add failing test for using single line breaks as per comment on #214
* Enable line break extension for single breaks in paragraphs by new lines.
Pass tests in ef3de607c3
* Enable GH flavour linebreaks in JS rendered markdown
* Made RML bullets pretty :)
* Added WYSIWYG editor. Works for notes & description, fails miserably for items :(
* Fixed for event items. Will probably fail tests because selenium can't type in simpleMDE :(
* FIX: Re-enable markdown on paperwork
Strikethrough is broken in all sorts of places for whatever reason
* FEAT: Markdown support on asset comments
* FIX: Prevent js injection through markdown fields
* Initial fixes
* Basic dark theme for simplemde
* Swap to locally delivered SimpleMDE
* Region for selenium testing of SimpleMDE
Bleh, Javascript all around
* Tests passing!
Fixed not using region for item modal, and overflow error on paperwork with really long description. Looks junk but I'm not really bothered
* Pep8 fixes
* Fallback for null HCapatcha sitekey
I.e. when we're on a branch
* Fix item description print being broken
* Actually fix sitekey problem
* Fixes for using markdown in asset comments
* Properly initialise markdown on asset comments
Co-authored-by: David Taylor <david@taylorhq.com>
Co-authored-by: FreneticScribbler <aj@aronajones.com>
* Upgrade to heroku-20 stack
* Move some gulp deps to dev rather than prod
* npm upgrade
* Fix audit time check in asset audit test
* Attempt at parallelising tests where possible
* Add basic calendar button test
Mainly to pickup on FullCalendar loading errors
* Upgrade python deps
* Tends to help if I push valid yaml
* You valid now?
* Fix whoops in requirements.txt
* Change python ver
* Define service in coveralls task
* Run parallelised RIGS tests as one matrix job
* Update python version in tests
* Cache python dependencies
Should majorly speedup parallelillelelised testing
* Purge old vagrant config
* No Ruby compass bodge, no need for rubocop!
* Purge old .idea config
* Switch to gh-a artifact uploading instead of imgur 'hack'
For test failure screenshots. Happy now @mattysmith22? ;p
* Oops, remove unused import
* Exclude tests from the coverage stats
Seems to be artifically deflating our stats
* Refactor asset audit tests with better selectors
Also fixed a silly title error with the modal
* Add title checking to the slightly insane assets test
* Fix unauth test to not just immediately pass out
* Upload failure screenshots as individual artifacts not a zip
Turns out I can't unzip things from my phone, which is a pain
* Should fix asset test on CI
* What about this?
* What about this?
Swear I spend my life jiggerypokerying the damn test suite...
* Does this help the coverage be less weird?
* Revert "Does this help the coverage be less weird?"
This reverts commit 39ab9df836.
* Use pytest as our test runner for better parallelism
Also rewrote some asset tests to be in the pytest style. May do some more. Some warnings cleaned up in the process.
* Bah, codestyle
* Oops, remove obsolete if check
* Fix screenshot uploading on CI (again)
* Try this way of parallel coverage
* Add codeclimate maintainability badge
* Remove some unused gulp dependencies
* Run asset building serverside
* Still helps if I commit valid YAML
* See below
* Different approach to CI dependencies
* Exclude node_modules from codestyle
* Does this work?
* Parallel parallel builds were giving me a headache, try this
* Update codeclimate settings, purge some config files
* Well the YAML was *syntactically* valid....
* Switch back to old coveralls method
* Fix codeclimate config, mark 2
* Attempt to bodge asset test
* Oops, again
Probably bedtime..
* Might fix heroku building
* Attempt #2 at fixing heroku
* Belt and braces approach to coverage
* Github, you need a Actions YAML validator!
* Might fix actions?
* Try ignoring some third party deprecation warnings
* Another go at making coverage show up
* Some template cleanup
* Minor python cleanup
* Import optimisation
* Revert "Minor python cleanup"
This reverts commit 6a4620a2e5.
* Add format arg to coverage command
* Ignore test directories from Heroku slug
* Maybe this works to purge deps postbuild
* Bunch of test refactoring
* Restore signals import, screw you import optimisation
* Further template refactoring
* Add support for running tests with geckodriver, do this on CI
* Screw you codestyle
* Disable firefox tests for now
That was way more errors than I expected
* Run cleanup script from the right location
* Plausibly fix tests
* Helps if I don't delete the pipeline folder prior to collectstatic
* Enable whitenoise
* Can I delete pipeline here?
* Allow seconds difference in assert_times_equal
* Disable codeclimate
* Remove not working rm command
* Maybe this fixes coverage?
* Try different coverage reporter
* Fix search_help to need login
* Made versioning magic a bit less expansive
We have more apps than I thought...
* Fix IDI0T error in Assets URLS
* Refactor 'no access to unauthed' test to cover all of PyRIGS
* Add RAs/Checklists to sample data generator
* Fix some HTML errors in templates
Which apparently only Django's HTML parser cares about, browsers DGAF...
* Port title test to project level
* Fix more HTML
* Fix cable type detail
