Thanks, this was due to a bug in how the hash identifier was being parsed. This issue has been fixed for the next version.