Packaging a plugin from Plugins Editor UI wipes the target folder before packaging

"Package Plugin" from Plugin Editor UI will wipe the target folder’s contents first then populate it with plugin files.

User was expecting “Package Project” like behavior: Create a new folder in the target folder, then put packaged files in the new folder, while deleting none of existing contents.

Compared with “Package Project”, "Package Plugin"'s wipe the target folder first behavior is destructive, might cause user data loss. User hopes "Package Plugin" would not delete existing folder contents.

0. Create a folder somewhere in PC, populate it with dummy files/folders(note: these will get deleted in step 5, do not put any important file)
1. Create a new C++ empty project
2. Add a "New Plugin" from Plugins Editor UI, use BlueprintLibrary template
3. Restart the editor
4. Show the newly created plugin in Plugins Editor UI, now "Package..." action is available
5. From "Package..." choose the folder created in step 0
6. Open the folder to see the plugin is packaged but all of existing dummy files/folders get deleted

Expectation: No existing files/folders get deleted like doing "Package Project"

How does TextureRenderTarget2D get TArray<uint8> type data?

Why does the REMOVE method of map container remove elements have memory leaks?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

trying to launch uefn and it is crashing and saying pakchunk4522 is courrupt, anyone have the fix for this?

Why does the volume fog disappear from a distant view?

How to convert the datasmith scene file to BluePrint. Create animations in BluePrint.

Does the pivot parameter setting in the actor's userinterface property relate to the Widget's anchor layout?

How to achieve HLSL Multiple Render Target in Material blueprints?

uefn session not lunching, wierd error