comunica / comunica/jQuery-Widget.js
Does changing log level affect the execution log in front end
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 43
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Currently in the source code the logger is set to info level.
I tried to adjust this by changing it to e.g. trace, logging the context before querying confirms that the logger is indeed changed to trace, but the outcome remains the same (in the execution log) and I do not get logs in console while in dev npm run dev or by building a static version and hosting it with http-server.
I am trying to achieve this because when encountering an UnauthorizedHttpError no results get shown not even those for which I was authorized. When using lenient mode to prevent this, the fact that I am unautherized doesn't get logged anymore.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with npm run dev, then with a static build served by http-server. Trace the logger configuration through the execution-log path, including the UnauthorizedHttpError and lenient-mode handling. Done means changing the log level produces the expected console or execution-log output and the authorized results and authorization errors are represented correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, jquery
- Domain
- frontend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100