gitea/modules/util
wxiaoguang 50a72e7a83
Use a general approach to access custom/static/builtin assets (#24022)
The idea is to use a Layered Asset File-system (modules/assetfs/layered.go)

For example: when there are 2 layers: "custom", "builtin", when access
to asset "my/page.tmpl", the Layered Asset File-system will first try to
use "custom" assets, if not found, then use "builtin" assets.

This approach will hugely simplify a lot of code, make them testable.

Other changes:

* Simplify the AssetsHandlerFunc code
* Simplify the `gitea embedded` sub-command code

---------

Co-authored-by: Jason Song <i@wolfogre.com>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2023-04-12 18:16:45 +08:00
..
filebuffer
error.go
file_unix.go
file_unix_test.go
file_windows.go
io.go
keypair.go
keypair_test.go
legacy.go
legacy_test.go
pack.go
pack_test.go
paginate.go
paginate_test.go
path.go Use a general approach to access custom/static/builtin assets (#24022) 2023-04-12 18:16:45 +08:00
path_test.go Use a general approach to access custom/static/builtin assets (#24022) 2023-04-12 18:16:45 +08:00
remove.go
sanitize.go
sanitize_test.go
sec_to_time.go
sec_to_time_test.go
shellquote.go
shellquote_test.go
slice.go
slice_test.go
string.go
string_test.go
timer.go Use a general approach to access custom/static/builtin assets (#24022) 2023-04-12 18:16:45 +08:00
timer_test.go Use a general approach to access custom/static/builtin assets (#24022) 2023-04-12 18:16:45 +08:00
truncate.go
truncate_test.go
url.go
util.go
util_test.go