Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

IR-3921: Copying resource should create a static-resource entry #10949

Merged
merged 5 commits into from
Aug 16, 2024

Conversation

CITIZENDOT
Copy link
Collaborator

@CITIZENDOT CITIZENDOT commented Aug 13, 2024

Summary

Currently, if we copy/paste a resource in studio's file browser, it does not create an entry in static-resource table. But it updates the existing entry with new key. This PR fixes it by identifying copy operations and creating a fresh entry for them.

Subtasks Checklist

Breaking Changes

References

closes https://tsu.atlassian.net/browse/IR-3921

QA Steps

Currently, if we copy a resource in studio's file browser, it does not create an entry in static-resource table. But it updates the existing entry with new key. This PR fixes it by identifying copy operations and creating a fresh entry for them.
@hanzlamateen hanzlamateen requested a review from HexaField August 13, 2024 07:28
@CITIZENDOT CITIZENDOT changed the title Copy operation should create a static-resource with create Copy operation should create a static-resource entry Aug 13, 2024
@CITIZENDOT CITIZENDOT changed the title Copy operation should create a static-resource entry Copying resource should create a static-resource entry Aug 13, 2024
@HexaField
Copy link
Member

Nice, let's add a regression test for this please.

@CITIZENDOT CITIZENDOT changed the title Copying resource should create a static-resource entry IR-3921: Copying resource should create a static-resource entry Aug 15, 2024
@HexaField HexaField added this pull request to the merge queue Aug 16, 2024
Merged via the queue into dev with commit 13ad7d1 Aug 16, 2024
25 checks passed
@HexaField HexaField deleted the use-create-for-copy branch August 16, 2024 00:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants