twig.sh
commits
The high-level API makes sense for cases, where the prompts and
resources are declared in the code and used to bind different functions
to implement them. In our case there is only one generic function that
reads prompts and resources from the local storage.
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>
The high-level API makes sense for cases, where the prompts and
resources are declared in the code and used to bind different functions
to implement them. In our case there is only one generic function that
reads prompts and resources from the local storage.
Signed-off-by: Jan Ehrhardt <59441+jehrhardt@users.noreply.github.com>