Thanks for the information, @BRVLN. I’ve looked at this more closely. This command is behaving as specified:
You can configure whether opening a
.hook file that contains a hook://file URL reveals the target file in the Finder, or opens it.
hook://file/ points to a folder or a file, the behavior is the same when configured to reveal the file in the target in the Finder. So, if Hook is set to reveal the target, when users activate the hook://file link, Hook opens the parent folder and selects the target. Whether the target is a file or folder, the effect is the same, which keeps things simple.
For users who would like to automatically open the folder on activating the link, they would either need to disable the checkbox, or create hook://file links to an item inside the folder.
Otherwise, we’d need to provide an additional preference like “if the target is a folder, don’t just reveal it but open it”. But I think the feature is currently subtle enough. Maybe an advanced (hidden) preference in the future.