The specification dictates that keywords should be case insensitive (e.g. AND vs and). This implements case insensitivity.
~Note: This implements the case insensitivity portion, though this implementation does technically allow for a combination of upper and lower case even though that is explicitly mentioned as not being necessary. If allowing combinations causes problems we can create an issue to handle that down the line.~
This PR includes an immediately stale commit which adds support for mixed case keywords; since the specification explicitly states mixed case should not be detected I took that support out. However, I'm keeping the feature in git history in case we change our minds down the line.
The specification dictates that keywords should be case insensitive (e.g. AND vs and). This implements case insensitivity.
~Note: This implements the case insensitivity portion, though this implementation does technically allow for a combination of upper and lower case even though that is explicitly mentioned as not being necessary. If allowing combinations causes problems we can create an issue to handle that down the line.~
This PR includes an immediately stale commit which adds support for mixed case keywords; since the specification explicitly states mixed case should not be detected I took that support out. However, I'm keeping the feature in git history in case we change our minds down the line.
Resolve #11