Support for dirty scheduler

Open
#25 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
erlang

Research direction

No files, tests, or entry points are identified in the issue. Start by determining the intended dirty-scheduler behavior and the affected integration points, then define tests and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Description

enhancement

I was wondering if it makes sense to add support for dirty schedulers and if so, if you have any plans for do it?

Dominant language
Erlang
Stars
137
Forks
44
Avg merge
3d 57m
Merged PRs (30d)
1

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.

More from processone/fast_xml

All issues in processone/fast_xml

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.