This fix should be available in your Slash GraphQL instance now.
Update - @pbassham sorry for the wrong info above. I confirmed with the Slash team and looks like the fix is not live yet on Slash. It should be available with the next release of Slash. You can monitor that at Topics tagged release