mirrors/gitea - gitea - source @ dussan.org

Autor	SHA1	Nachricht	Datum
silverwind	e03d627769	Misc JS linting and naming tweaks (#10652) - lowercase all js filenames except Vue components - enable new lint rules, mostly focused on shorter code - autofix new lint violations - apply misc transformations indexOf -> includes and onevent-> addEventListener Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>	vor 4 Jahren
silverwind	fdf6d25915	Reorganize frontend files and tooling (#10168) - move "vendor" files to js/vendor and less/vendor - move swagger to js/standalone (meant for standalone pages) - move gitgraph to features and streamline its loading - add linting configs to webpack dependencies in make - set ignored files for eslint/stylelint directly in their configs Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: zeripath <art27@cantab.net> Co-authored-by: Antoine GIRARD <sapk@users.noreply.github.com>	vor 4 Jahren
silverwind	7c84dbca4f	fix gitgraph commit hashes in dark theme (#10046) because the CSS was lazy-loaded the rules in arc-green did not win. included the css file in the main bundle to fix. the black dots can not be fixed via CSS because they are drawn in a `<canvas>` element unfortunately.	vor 4 Jahren
silverwind	7bc8c6b180	move semantic.dropdown.custom.js to webpack (#9064) * move semantic.dropdown.custom.js to webpack Also disabled a annoying linter rule which insisted that imports can not contain a file extension. Fixes: https://github.com/go-gitea/gitea/issues/8971 * reorganize web_src files and rebuild * restart ci	vor 4 Jahren
silverwind	f8bd90ba60	enable lazy-loading of gitgraph.js (#9036) - moved gitgraph.js to web_src and made it importable and es6-compatible - created new webpack chunk for gitgraph - enabled CSS loader in webpack - enabled async/await syntax via regenerator-runtime - added script to ensure webpack chunks are loaded correctly - disable terser's comment extraction to prevent .LICENCE files gitgraph.js has many issues: 1. it is incompatible with ES6 because of strict-mode violations 1. it does not export anything 1. it's css has weird styles like for `body` 1. it is not available on npm I fixed points 1-3 in our version so it's now loadable in webpack. We should eventually consider alternatives.	vor 4 Jahren