API endpoint filter slug with one character throwing error

[emilgoldsmith]

Welcome to Ghost's GitHub repo! 👋🎉

Do you need help or have a question? Please come chat in Slack: https://ghost.org/slack 👫. Got an idea for a new feature? Please add it to our wishlist: http://ideas.ghost.org 🌟. Found a bug? Please fill out the sections below... thank you 👍

Issue Summary

When accessing the API endpoint for getting posts with a filter query of a slug with just one character it throws the following error:

ERROR: Query Error: unrecognized text "v" in filter at char 6
slug:v

I know you wouldn't generally want to use a 1 character slug and it's really stupid etc. but the editors of the blog I develop for apparently screwed up a couple of years ago I just realized. Even though 1 character slugs are stupid, I'm assuming this is not intended behaviour, yeah?

Steps to Reproduce

You can for example use these query params for your call: filter=slug:a&fields=slug,html,image,meta_description,title&limit=1

Technical details:

• Ghost Version: 0.11.7
• Node Version: 4.2
• Browser/OS: Browser N/A (fetched serverside through Node.js request) on Ubuntu 16.04
• Database: MySQL (MariaDB)

[emilgoldsmith]

Also, btw I've hotfixed it by adding quotes ' around the slugs as that's what I did to fix a previous issue I submitted here which was a slug starting in a number until it was fixed. But just thought I should still report it as I don't believe it is intended behaviour.

[kirrg001]

Hey @emilgoldsmith 👋

Thanks for your bug report. Sounds like a bug in our GQL parser.
If somebody wants to pick this bug up, we would be thankful 🙃

[ErisDS]

I've raised TryGhost/GQL#24 to track this issue. Short term, using quotes is not really a hotfix as it were. GQL supports the concept of literals - these are strings that don't require quotes. They're a special case built for simplicity, and they do have limitations.

Using a string, which is more reliable, is a perfectly sensible workaround.

Nonetheless, this limitation is a surprise to me, it's not documented nor covered by tests. Therefore it warrants and issue and investigation to see if we can fix it without breaking everything else ;)