Reproducible on MacOS, but potentially the same issue affects Windows and Linux
How to reproduce:
1. View the attached file's "plugin.bundle" contents
2. Create a project with the default 3D template
3. Make the .meta files visible (Edit->Project Settings->Editor->Version Control->Mode)
4. Import "plugin.bundle" to the project
5. View the imported file's contents
Expected result: Meta files are not created inside the .bundle files
Actual result: Meta files are created inside the .bundle files
Reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.3.12f1, 2020.1.0b8, 2020.2.0a9, 2023.1.0a3 (checked)
Additional requirements:
| Item |
Status |
| Disallow Drag and Drop into Bundle folders |
✔️ |
| Disallow Drag and Drop when multiple assets are selected |
✔️ |
| Prevent .meta file creation |
✔️ |
| Do not show plugin folders as folder in project browser two column view |
✔️ |
| Do not show plugin folders as folders in project browser one column view |
✔️ |
| Handle DirectoryMonitor message when deleting an already existing .meta file in a plugin folder correctly |
✔️ |
| Write tests that ensure the AssetDatabase.ValidateMoveAsset and AssetDatabase.MoveAsset APIs don't allow moving assets into loadable plugin directories |
✔️ |
| Update AssetDatabase.MoveAsset & AssetDatabase.ValidateMoveAsset documentation to mention new restriction |
❌ |
| Write test to ensure folders named "bundle", "framework", etc. are still imported |
✔️ |
| Write test to ensure folders named "bundle", "framework", etc. can have assets moved into them |
✔️ |
| Write test to make sure you can move a loadable plugin folder to another folder with no imports on its children happening |
✔️ |
| Reimporting loadable plugin directories should not import their contents |
✔️ |
| Reimporting parent folders of loadable plugin directories should not import the loadable plugin directories' contents |
✔️ |