allowed_symlinks.txt requires exact relative path of symlink target instead of resolved absolute path

When symlinking a datapack I’m developing into my world/datapack folder, I get the “disallowed symlink” error
[19:44:17] [Render thread/WARN]: Failed to validate 'C:\Users\MagicJinn\AppData\Roaming\PrismLauncher\instances\1.21.8\minecraft\saves\New World'. Found forbidden symlinks: C:\Users\MagicJinn\AppData\Roaming\PrismLauncher\instances\1.21.8\minecraft\saves\New World\datapacks\MagicJinns-Minecraft-Tweaks->..\..\..\..\..\..\..\..\..\Documents\GitHub\MagicJinns-Minecraft-Tweaks`

While I put the full path in my allowed_symlinks.txt file:
C:\Users\MagicJinn\Documents\GitHub\MagicJinns-Minecraft-Tweaks
This was because it was actually expecting the relative path

..\..\..\..\..\..\..\..\..\Documents\GitHub\MagicJinns-Minecraft-Tweaks
This feels like unintended behavior