Import improvements
Open
Nobody has claimed this yet.
enhancement
import/export
overview
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
- https://github.com/nextcloud/tables/issues/833
- https://github.com/nextcloud/tables/issues/365
- https://github.com/nextcloud/tables/issues/838
- https://github.com/nextcloud/tables/issues/836
- https://github.com/nextcloud/tables/issues/837
Further ideas to be filed separately:
- Collect and list failed rows and columns instead of just counting
- The backend code could need some refactoring
- Skip empty rows if detected https://github.com/nextcloud/tables/pull/845#issuecomment-1969322148
- If we have failed rows collected, allow to manually adjust them
- Epic: We could dryrun the import and present the user with the expected outcome in table column format and a preview
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 reviewing the linked issues 833, 365, 838, 836, and 837, then separate the unchecked ideas from the completed work. The issue does not name files, tests, or an entry point; it is done only when a specific import improvement is scoped and its expected behavior is defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100