[Proposal] Rename Sequence transformation to avoid clashes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
When type-hinting my code, I frequently need Sequence from collections.abc. In order to avoid name clashes, one can do for either of the two:
from spatialdata.transformations import Sequence as SequenceTransform
I've noticed that by now all my imports are like this.
A good name could be TransformationSequence (which reads as "a sequence of transformations"), or SequenceTransformation (analog to BaseTransformation) or anything shorter. On the other side, all specific transformation classes don't have it in their name (Affine etc.).
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 inspecting the public spatialdata.transformations module and searching for the current Sequence name and its imports. Review how the proposed replacement would affect transformation classes and consumers; done means one agreed name is applied consistently without leaving the existing clash unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100