Open-EO / Open-EO/openeo-python-driver
Simplify SaveResult class hierarchy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
Current SaveResult class hierarchy is pretty complicated :
I always find it confusing to work in this area, especially with all these Aggregate* classes.
Ideally, fully migrating to proper vector cubes (#114) will eliminate a large part of this hierarchy, but maybe there are some quick wins before that
Contributor guide
No contributing guide indexed for this repository
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 SaveResult class hierarchy and the Aggregate* classes referenced in the issue, then review issue #114 on proper vector cubes. Identify a bounded simplification that can be made before that migration; done should mean a demonstrably simpler hierarchy without breaking existing SaveResult behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100