Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

improve table linking

Open
#195 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
r
Domain
data

Research direction

Start by reading the three helpers in utils.R: .sync_tables_sdattrs, .sync_shapes_on_drop, and .sync_tables_on_drop. Compare their behavior with the object-wide .zattrs design draft linked in the issue, then inspect existing tests for table, shape, and label links. Done means the current R implementation is clearer and its link behavior is covered by tests.

Written by the indexing model from the issue text.

Description

  • We currently have a few helpers to help keep coherent links between tables & shapes/labels; in utils.R:
    • .sync_tables_sdattrs updates table spatialdata_attrs
    • .sync_shapes_on_drop filters observations in linked shapes
    • .sync_tables_on_drop filters tables when dropping shapes/labels
  • A design draft to keep all links as object-wide .zattrs is here
  • Since this could take a while, might be worth to see how we can improve & test more the current R implementation; it is quite in-elegant and confusing...
Dominant language
R
Stars
37
Forks
10
Avg merge
22h 46m
Merged PRs (30d)
20

Getting set up

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 HelenaLC/spatialdataR

All issues in HelenaLC/spatialdataR

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.