redpanda-data / redpanda-data/connect
Lint errors could give hints on indentation problems
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
For example, with the following config:
output:
switch:
retry_until_success: false
cases:
- check: errored() && meta().error_count.number() > 100
processors:
- log:
level: DEBUG
message: 'dropping message due to error_count over threshold.'
output:
drop: {}
We give the error field processors not recognised, it'd be much more useful if we could detect the fields of siblings and the parent in order to give a message like field processors not recognised, consider moving it within the field "output".
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
Use the YAML example and target error as the acceptance reference. No file or test is named, so start by locating the validation path that emits “field processors not recognised” and inspect how parent and sibling fields are available. Done means misplaced fields can produce a useful relocation hint while existing validation remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, yaml
- Domain
- stream-processing, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100