Adaptor debug logs are weird
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Not sure what this issue is yet!
If in an adaptor I do console.debug, a few strange things happen:
In the CLI, the log seems to get duplicated if I run with --log debug:
[R/T] ❯ Starting operation 2
Collections: Downloading data from "demo"...
Collections: fetched chunk of 0 values from "demo"
Collections: Fetched total of 0 values from "demo"
[JOB] ℹ Fetched 0 items
With default logging, the adaptor's console.debug line seems to still appear:
Collections: Downloading data from "demo"...
Collections: fetched chunk of 0 values from "demo"
Collections: Fetched total of 0 values from "demo"
Obviously note that in the CLI, we don't see any level or namespace information here. This is known to me (although I don't think I have an issue for it...)
In Lightning, the same debug line doesn't seem to appear at all:
ADA Collections: Downloading data from "demo"...
ADA Collections: Fetched total of 0 values from "demo"
This must be something to do with how I'm overriding the console global in the adaptor....
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 tracing the adaptor's console-global override and compare how logging is handled in the CLI and Lightning entry points. Reproduce the console.debug examples with --log debug and default logging, checking for duplication and filtering differences. Done means adaptor debug output is consistently handled without unexpected duplication or disappearance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100