decisions: shorten links
## Problem
-In the previous error concept it was very useful to generate macros as we often added new errors. The code generation itself, however, is quite complicated (C++ code that prints the code; which is also not ideal for cross compilation, see also https://github.com/ElektraInitiative/libelektra/issues/2814).
+In the previous error concept it was very useful to generate macros as we often added new errors.
+The code generation itself, however, was not ideal for cross compilation.
## Constraints
@@ -15,9 +16,9 @@ In the previous error concept it was very useful to generate macros as we often
- Migrate to a more modern and easier way to generate code with our mustache system, and let this generate the (mapping) code for all compiled languages (C, C++, Java, Rust, Go).
All we get out of this is the removal of `std::cout << ...` code from C++ but not much more.
-- Migrate to CMake code that generates such macros/classes (see also https://github.com/ElektraInitiative/libelektra/issues/2814)
+- Migrate to CMake code that generates such macros/classes.
Mustache templates have to be supplied with the input data somehow. Either we have to use a custom executable that is compiled at build time.
- In that case we would just get rid of the std::cout << ... in the C++ code, but not much else would change.
+ In that case we would just get rid of the `std::cout << ...` in the C++ code, but not much else would change.
The other option is to use the default mustache executable, which is a Ruby script and therefore requires Ruby to be installed.
Also kdb gen cannot be reused, since that would require compiling kdb first, which needs kdberrors.h.
@@ -44,5 +45,5 @@ When adding a new error code, language bindings have to be adapted accordingly s
## Notes
-- https://github.com/ElektraInitiative/libelektra/issues/2871
-- https://github.com/ElektraInitiative/libelektra/issues/2814
+- See also [Issue #2814](https://issues.libelektra.org/2814)
+- See also [Issue #2871](https://issues.libelektra.org/2871)
