ukaea / ukaea/Multiparser

Support starting from a given point in a file

Open
#199 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Description of the Issue/Problem to address
I would like to have an option where eg if when I start Multiparser, a file it is tracking already exists, it doesnt do anything with the already existing data, and just keeps an eye on changes from that point.

Proposed solution
When multiparser first loads, just skip any parsing / callbacks which would typically be triggered, and record the current state of the file as the last parse

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing Multiparser's startup path and the code that records tracked-file state and invokes parsing or callbacks. Define the option's expected startup behavior, then verify that an existing file is treated as the current baseline while later changes still trigger normal processing.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.