-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for copying and pasting features in the feature grid #10563
base: master
Are you sure you want to change the base?
Add support for copying and pasting features in the feature grid #10563
Conversation
- Implemented [`copyFeatures`] epic to handle the COPY_FEATURES action: - Retrieves the current state from the store. - Uses to get the selected features. - Stores the selected features in [`localStorage`] as a JSON string to facilitate copying to the clipboard. - Implemented [`pasteFeature`] epic to handle the PASTE_FEATURES action: - Currently returns an empty observable, ready for future implementation. - Will retrieve the copied features from [`localStorage`] for pasting.
@mdelsinne44 thank you so much for contributing to MapStore. Is there an issue related to this? |
No, I don't think so. It's an enhancement I developed to meet a client's need, allowing entities to be copied from one layer to another. For example, from a shapefile to a WFS layer. The functionality allows copying the geometry as well as all the corresponding fields from one layer to another. |
Thank you @mdelsinne44 for the feedback. If you can, please open an issue to describe the feature and put a link in PR description as indicated by the PR template. If you cannot, don't worry, we will do it for you just before the review. Thank you so much again for contributing to MapStore. |
@mdelsinne44 one of our checks is failing due to missing mandatory translations it seems. Can you fix it? |
I think it's good for the translations |
Description
copyFeatures
epic to handle the COPY_FEATURES action:pasteFeature
epic to handle the PASTE_FEATURES action:Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
#10566
What is the new behavior?
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information