Plain text ingestion improvements/tasks
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 167
- Forks
- 30
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 9
Description
From #19
- Extend
--invalid-data=to includereportas an option, so that "orphan"/un-parseable lines can be captured -
--testflag that prints JSON to STDOUT instead of sending events to Seq (could perhaps be called something like--echoor--dry-run?) - List the built-in matchers in the README
- Sanity check the (future) story for optional (
{:?), parameterized (digit(4)) and regex matchers
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 reviewing the plain-text ingestion work referenced from issue #19 and the CLI handling for --invalid-data. Done would require resolving the requested report mode, a test or dry-run output mode, README matcher documentation, and the future matcher syntax questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100