Deletion of supposedly .filenignored cloud folder not ignored locally

[pgpbj]

Describe the bug
It is possible to induce an undesired local data loss by deleting a cloud folder even when the folder is listed in the .filenignore file.

To Reproduce
Steps to reproduce the behavior:

1. Create a local test folder 'A'. Create file Document.txt inside folder A.
2. Create subfolder 'B' inside A. Create file 'importantDocument.txt' inside B.
3. In Filen UI, select 'Syncs' tab. Create new Sync:
   3.1 Local path: path to folder A
   3.2 Cloud path: new cloud folder
   3.3 Sync mode: 2-way
4. Click on Sync Settings-> .filenignore. Enter "B/" to cause subfolder B to be ignored during sync. Verify that 'Disable local trash' is not enabled
5. Un-pause (Resume) Sync created in step 3
6. In browser, browse to Filen.io to confirm what has been synced to the cloud

Expected behavior
File Document.txt should be synced. Unclear if Subfolder B should be synced.

Actual behavior
File Document.txt IS synced to the cloud. Subfolder B IS synced to the cloud, but it is empty (i.e. importantDocument.txt is not synced). Unclear if this behavior is correct, but it seems acceptable, so far.

7. In browser, click on ellipsis to the right of folder B; select red 'Trash' menu item.
8. View confirmation dialog ("Are you sure you want to send B to the trash? You can always recover it afterwards."). Click on 'Trash' button.

Expected behavior
Unclear, but since folder B is listed in .filenignore, I was expecting that folder B would remain on the local computer.

Actual behavior
Folder B is deleted from both cloud and local computer. The content of folder B (i.e. importantDocument.txt) is also deleted from the local computer. There appears to be no backup of importantDocument.txt on cloud or local computer, file is lost.

OS:

• OS: Linux Mint 21.3 Cinnamon
• Hardware configuration: Proxmox VM with 4 CPU, 4GB RAM, 80GB virtual disk
• Filesystem and Disk type: ext4 on VirtIO SCSI disk.

Additional context

1. Filen linux AppImage x64 Intel/AMD build 3.0.41.
2. I have observed the same behavior running Linux Mint 21.3 Cinnamon on bare-metal x64 Intel hardware
3. Sometimes an subfolder B will be recreated in the cloud following steps 7 & 8. In this case, repeating steps 7 & 8 will reproduce the problem.