pre/post data processors to use range/domain terminology?

Open
#610 2 comments 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
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start by locating the pre/post data processor definitions and the projector pair APIs referenced in the issue. Trace every use of the current pre-forward and post-back terminology, then determine the complete naming and compatibility scope before updating references and relevant tests.

Written by the indexing model from the issue text.

Description

Might be worth considering changing our pre/post data processors to using range and domain terminology.

That way, pre-forward and post-back data processors would both have the same name. They could then be set via the projector pair, and still be explicit as to what they'll act on.

Dominant language
C++
Stars
160
Forks
113
Avg merge
12d 15h
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 UCL/STIR

All issues in UCL/STIR

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.