Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handlebars template/helper for outputing texts and logging at the same time. #45

Open
RieksJ opened this issue Apr 1, 2024 · 2 comments

Comments

@RieksJ
Copy link
Member

RieksJ commented Apr 1, 2024

@Ca5e : The TRRT configuration for tev2-specifications should have an error-converter that simply outputs the showtext, AND logs that it didn't find an MRG entry. I have tried this as follows:

image

This works in the sense that I can see logs for entries that do not exist.

However, it also produces this error at the beginning of the TRRT log:

image

And further on, there are lots of log lines such as this:

image

How can we do this (simply output the showtext, AND logs that it didn't find an MRG entry) without getting all these errors?

@RieksJ RieksJ changed the title Handlebars helper needed for outputing texts and logging at the same time. Handlebars template/helper for outputing texts and logging at the same time. Apr 1, 2024
@Ca5e
Copy link
Member

Ca5e commented Apr 7, 2024

@RieksJ could you revisit this issue with the newest run of tev2-specifciations that uses the newest published packages?

@RieksJ
Copy link
Member Author

RieksJ commented Apr 8, 2024

It still has the problems.

Line 138 in the log-shot below (see this log) says there is some error, which I assume is related to the error converter:

image

However:

  • the log seems to be ok, and when I look at the converted results (being the showtexts), that seems to be ok as well. We expect all these warnings as they relate to glossary entries from the eSSIF-Lab scope (related to How to treat 'imported' TermRefs such that they become convertable #25).
  • the log also shows Term Errors of the kind TERM HELP (see log-shot below). While such messages are helpful initially, they may also clobber the log in cases such as we have now. @case: do you have a suggestion for how we can make this optional somehow?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants