DigitalCommons / land-explorer-front-end

React app for the Land Explorer front end
http://landexplorer.cc
GNU Affero General Public License v3.0
1 stars 0 forks source link

[LX Collab Mapping] Read, write, own map permissions #307

Closed lin-d-hop closed 3 months ago

lin-d-hop commented 5 months ago

Please track under the clockify project [LX Collab Mapping]

Description

Following on from #304 Currently users can own maps that they create. They can share these maps as read-only with other users.

We want to implement three levels of map permissions: Read - as per the current read only, the user can see the map and interact with elements but cannot add or edit the map Write - the user can see the map, interact, add and edit elements on the map. Own - as per the current owner. Can write. Can also delete the map and share the map with other users.

Additional complications arise with write are explored in #306, which is likely a prerequisite for this piece.

Acceptance Criteria

ms0ur1s commented 5 months ago

Not sure how long this hasn't worked for, but get the same result both locally and live (now resolved) locally. So map sharing's not working.

image

image

Changes to mapSharing function

image

image

ms0ur1s commented 5 months ago

Read and write permission pushed to the BE, base on FE selection. Only map owner status is outstanding.

image

lin-d-hop commented 4 months ago

@ms0ur1s How's this work coming along? Will be great ot be new and improved map sharing online :)

ms0ur1s commented 4 months ago

@ms0ur1s How's this work coming along? Will be great to be new and improved map sharing online :)

Hi @lin-d-hop, apologies, as with #308 the hold-up is #306 which I'll organise to Rohit so we can resolve it.

rogup commented 3 months ago

@ms0ur1s are you creating a UI for a map owner to assign either write or read permissions to another user? It's not clear whether this is in the scope of the issue

ms0ur1s commented 3 months ago

Hey @rogup, yep that was done in either #306 or #308.

rogup commented 3 months ago

This work will be done within the PR linked to #306