* 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
Another silly copy paste error from ECs. Also really makes me want 'repeatable fragments' in Django templating so that the top and bottom page buttons could actually be the same...
* Add button for creating forum thread draft from event detail
TODO: Allow RIGS to ingest POST requests sent from the forum on new posts in RIG info to link up the forum thread
RE https://forum.nottinghamtec.co.uk/t/rigs-discourse-integration/15592/21
* Mockup webhook recieving view
* Correct method of CRSF exemption for webhook reciever
* Use f-strings correctly, not like a big dumb
* That was also dumb, fix that too
* Second shot at webhook reciever
* Oops
* >.<
* Third shot
* Try again at signing
* What if I gave it the right arguments. That might be a good start.
* More fiddling with auth
* Add debug print
* Okay, put that back where it was because I inavertently overloaded my import
Flashbacks to my java days...
* Different header access method
* Fix import, again
* Fix ommited json parsing wotsit
* Fix url
* Fix string index
* Correct template logic
* Allow manual adding/editing of URLs
* Filter by right flavour of event
* Amend event str conversion for consistency
* Oops
* Make migration
Will be squashed later
* Fix logic when creating events
* Squash migration
* Implement codedoctor suggestion
* Add absolute URL to power tests
* Update to target Python 3.10
* Return user to current page when clicking 'mark reviewed'
* Add units to power test record detail and form
I'm a bad scientist (coz I'm an engineer)
* Allow a higher value in PSSC fields
* Default venue to event venue in EC/PT
* Fix population of initial venue values for EC/PT
* Add link to create power test from EC detail
* Do not set power plan field to required on RA
"This might be a problem if the risk assessment is being done by one person and the power plan by another."
* Default power MIC to MIC
* Implement some suggestions from the Doctor
* Prevent checking in to cancelled events and dry hires
Will close#539
* Exclude dry hires from H&S overview list
* Add "ex VAT" tooltips to asset purchase price and replacement cost
* Automagically clear and focus ID field when audit modal closes
Closes#533
* Delete unused things
* Allow two decimal places in cable length, show training item IDs in selectpicker
Will close#540
* Fix#524 500 Error when viewing qualification list for items nobody is qualified in
* Update README.md
* Add a guard against nulls in recent changes
Maybe fixes#537 I'm unable to replicate locally
* Turn down verbosity of CI tests, fix tests, potential speedup
* Squash migration
* Add encoding to open
* Update to v3 upload-artifact
Resolves a deprecation warning
* Split power related parts of event checklist into a seperate form
* Revamp H&S overview, remove individual lists.
They were not a good thing.
* Remove old 'vehicle/crew' stuff
* Very initial version of checkin form
* Further work on checkin, add role field etc
* Fix tests after form split
* Add ability to edit checkins, more validation
* Basic checkin/out logic complete
* Add homepage checkin for events happening now
* Minor improvement to homepage UI
* Checkin button turns into checkout button where applicable
* UI work
* Clicking check out does not redirect the user
* Register check in model with the admin site
* Add power record status chip, checklist status chip displays number of checklists
* Minor fixes
* Implement codedoctor suggestions
* pep8
* Add data migration for crew/vehicles
* Checkin only requires login (no perms) and block users from editing other checkins at Django level
* Add 'description' field to TrainingItems
Renamed existing field to name, removed the dummy property.
* Initial version of training item export view
* Fix line length issue and better spacing on exported PDF
* Added export button to item list
* pep8
* Implement code doctor tweaks
* Attempt to fix odd deployment issue
* Pad headers slightly
* Fix page numbering
* 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>
