First node dropped into empty tree not triggering onNodeDrop

[leifjones]

I'm submitting a ... (check one with "x")

[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Plunkr Case (Bug Reports)
https://stackblitz.com/edit/primeng-treedragdrop-demo-ws7uey?file=src%2Fapp%2Fapp.component.ts

Current behavior
Given that there are no nodes within a (droppable) target tree,
When a node is dragged and dropped into the previously empty target tree,
Then the target tree's onNodeDrop function is NOT called.

(The onNodeDrop function IS called when there are already nodes in the target tree.)

Expected behavior
Given that there are no nodes within a (droppable) target tree,
When a node is dragged and dropped into the previously empty target tree,
Then the target tree's onNodeDrop function IS called (as with subsequent drops).

Minimal reproduction of the problem with instructions

1. Configure:

• a droppable tree with no initial treenodes, and a function listening to the onNodeDrop event
• a second draggable tree with treenodes

2. Load page
3. Drag a node from the source tree to the target tree
4. Note that the listening function is not triggered for the first drop

What is the motivation / use case for changing the behavior?
We have validation and transformation logic with a function that listens to the onNodeDrop events. But this is not occurring for the first drop.

Please tell us about your environment:

• Angular version: 11.2.4

• PrimeNG version: 11.3.0

• Browser: Chrome 88.0.4324.190 (only one checked so far)

• Language: TypeScript 4.0.5, module: es2020, target: es2015

• Node (for AoT issues): node --version = 14.5.3

[leifjones]

@yigitfindikli We're respectfully curious - so we can decide whether to code around this bug: How soon might the 11.3.2 release occur?