If there are multiple agents with the same variation name, this was not taken into account when hashing the child branch names and led to accessing the wrong context.
I have aligned the layout of the hashBranchChildNames with the computeBranchChildNames by adding distinct clauses based on the path size, so that the variations are handled correctly by also taking the agentType into account
This PR addresses the bug described in Issue #16.
If there are multiple agents with the same variation name, this was not taken into account when hashing the child branch names and led to accessing the wrong context.
I have aligned the layout of the
hashBranchChildNameswith thecomputeBranchChildNamesby adding distinct clauses based on the path size, so that the variations are handled correctly by also taking the agentType into account