OpenFn / OpenFn/lightning

Allow users to share a collection with other projects.

Open
#2,855 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

As a project owner or admin, I would love to be able to share my project collection with another project. By sharing the collection with the project, I don't need to pay for new collections or duplicate data across multiple projects (which can be hard to manage).

Notes:

  • When we list collections in a project, we should indicate the projects that have access to a collection on the collections list.
  • When sharing a collection with another project, we should block the share if the receiving project has a collection that has the same name as the shared collection.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue names no files, tests, or entry points. Start by tracing how project collections are listed and how collection access is managed, then identify the flows for sharing with another project. Done means shared collections show their accessible projects and sharing is blocked when the receiving project already has a collection with the same name.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.