* Remove useless divider-spans from toolbar and change css-selector
The use of extra divider elements is not needed as we can set the css-after pseudo-class to the button groups with the same styling.
This way we can reduce the amount of elements in the DOM by a hand full.
* Use scss syntax and include one rule into another more common one
* added missing autocompletions:
- code-block
- container
- header
- image
- link
- pdf
* added extraTags ([name=], [time=], [color=]) to the link autocompletion, because they trigger on the same characters
added getUser in /redux/user/methods to retrive the current user outside of .tsx files
improve the regexps on several autocompletion
* renamed hints to auto
Co-authored-by: Erik Michelson <github@erik.michelson.eu>
Co-authored-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
* Add 'yarn lint' command and run it in GH actions
* Move linting to own workflow
* Remove linting from build-workflow
* Solve linting warnings
Signed-off-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
Co-authored-by: Tilman Vatteroth <tilman.vatteroth@tu-dortmund.de>
- added csv-replacer
- changed highlghted-code plugin:
each replacer extracts what he need from the data-extra attribute now
- changed CHANGELOG.md
Co-authored-by: Erik Michelson <github@erik.michelson.eu>
This fix needs a little bit of explanation. Normally the 'keyUp' prevent is preferred because it fires after being sure, that not some buttons more belong to the shortcut. Additionally some platforms set the key-property of the 'keyDown'-event to the composition result of the key-combination thus resolving under certain environments to '€' while in other environments to 'e'.
The browser's event flow is as following: keyDown -> keyPress -> textInput -> keyUp.
As the keyUp-event is too late (after textinput) and the keyPress-event does not work properly with the modifiers, we felt compelled to use 'keyDown' and watch for 'e' as well as '€' key-properties. If some other keyboard locale does output different characters than these two, that person got a problem - meaning no functionality of the shortcut. But still better than nothing.
While running tests, cypress records videos of each one and processes them afterwards. This needs some resources we could save to reduce the CI runtime as we don't use or upload these videos.
