redpanda-data / redpanda-data/console
console.log in JavaScript filtering
Open
Nobody has claimed this yet.
backend
frontend
ui/ux
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
Hello,
In the JavaScript filtering, I can't use console.log(...) to debug my filter.
It can be really useful as sometime I don't really know what JavaScript object I'm manipulating...
Contributor guide
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 locating the JavaScript filtering entry point and checking how filter expressions are evaluated and where their output or errors are surfaced. Confirm the intended debugging behavior for console.log(...) and consider how to verify that logged JavaScript objects are visible to users; done means filtering users can inspect those values while debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100