15a8acbd6c
MRF, Docs.Generator: Ensure code is loaded before checking it
2023-11-30 09:40:17 +04:00
e853cfe7c3
Revert "Merge branch 'copyright-bump' into 'develop'"
...
This reverts merge request !3825
2023-01-02 20:38:50 +00:00
10886eeaa2
Bump copyright year
...
Signed-off-by: marcin mikołajczak <git@mkljczk.pl>
2023-01-01 12:13:06 +01:00
1d7e8d6e01
Pass in msgctxt for config translation strings
2022-07-14 17:41:33 -04:00
7473868880
Fix compile error
2022-07-13 18:46:21 -04:00
b2a0718e83
Extract config descriptions for translation
2022-07-13 18:01:47 -04:00
17aa3644be
Copyright bump for 2022
2022-02-25 23:11:42 -07:00
c4439c630f
Bump Copyright to 2021
...
grep -rl '# Copyright © .* Pleroma' * | xargs sed -i 's;Copyright © .* Pleroma .*;Copyright © 2017-2021 Pleroma Authors <https://pleroma.social/ >;'
2021-01-13 07:49:50 +01:00
485697d96c
config descriptions for custom MRF policies
2020-11-10 19:20:14 +03:00
8539e386c3
Add missing Copyright headers
2020-10-12 12:00:50 -05:00
4347d2de5e
Config/Docs: Expand behaviour suggestions at runtime
2020-07-12 17:23:33 +02:00
a2fcfc78c9
Filter config descriptions by config whitelist
2020-05-12 21:07:33 +01:00
282a93554f
merging release default config on app start
2020-03-11 16:25:53 +03:00
c55301e760
Fix a compilation error under certain circumstances
...
I've noticed that sometimes when switching from develop to stable and back,
develop fails to compile and rm -r ing the _build and deps dirs doesn't
help at all.
This is due to Admin API controller needing to generate JSON description
of the config at compile time. Evaluating `config/description.exs`
calls `Generator.list_modules_in_dir/2`, which in turn predicts the
module names of files in the directory and tries to convert the
predicted name to *existing* atoms. Sometimes the compiler will
call that function before compiling the modules in the said directory,
so the conversion will of course fail.
This fixes it by removing the requirement of the atoms being existent.
The function is not subjected to any untrusted user input so this should
be safe. An ideal fix would be to block the compilation of docs before
all modules are compiled and then get a list of compiled elixir modules
under the namespace we want instead of directory hacks, but I have not
been able to figure out how to do that.
2020-02-10 18:41:02 +03:00
7676ed8239
some clean up
2020-01-17 16:28:44 +03:00
cda2c1fc63
fix for subgroup tuple
...
added settings for swoosh adapters local
2020-01-10 15:52:01 +03:00
2753285b77
config editing through database
2020-01-10 15:51:59 +03:00
6a4201e0b4
fix for migrate task
2019-11-10 22:54:37 +03:00
e501c822c9
markdown.ex: put two-spaces before the description-newline
2019-09-17 23:05:27 +02:00
4785596a2c
markdown.ex: end suggestions list with a newline
...
Otherwise we end up with suggestion on the same level as the childs
Markdown is a fuck…
2019-09-17 23:05:27 +02:00
d2097fd0f5
markdown.ex: \n\n on >1 suggestions, 2-spaces on one
2019-09-17 23:05:27 +02:00
d6182a3c8f
markdown.ex: Make suggestion(s) plural only if on >1
2019-09-17 23:05:27 +02:00
c0c5628200
description.exs: remove empty strings on descriptions
2019-09-17 23:05:26 +02:00
106afaed58
markdown.ex: do not fail if there is no children
2019-09-17 23:05:26 +02:00
e0d8c8897e
docs/markdown.ex: do no print empty suggestions
2019-09-17 23:05:26 +02:00
7f211a48e0
docs/markdown.ex: child header as "- key (type): description"
2019-09-17 21:47:32 +02:00
69faec031d
markdown generation to the new file
2019-09-13 19:02:42 +03:00
be32d90a0c
little refactor
2019-09-11 09:25:33 +03:00
5ff12e7df1
some changes
2019-09-11 09:25:33 +03:00
35757b6d0e
don't add behaviour to suggestions
2019-09-11 09:25:33 +03:00
0624e06a9c
little fix
2019-09-11 09:25:33 +03:00
6721301086
some changes
2019-09-11 09:25:33 +03:00
67e4300931
description formatters
2019-09-11 09:25:33 +03:00
Lain Soykaf