Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure CEL lexis is compatible with Google SQL #45

Closed
3 tasks done
TristonianJones opened this issue Jun 4, 2018 · 0 comments
Closed
3 tasks done

Ensure CEL lexis is compatible with Google SQL #45

TristonianJones opened this issue Jun 4, 2018 · 0 comments
Assignees
@TristonianJones
Labels
bug Something isn't working

Comments

@TristonianJones
Copy link
Collaborator

Issue Filing Checklist

  • There are no issues that match the desired change
  • The change is large enough it can't be addressed with a simple Pull Request
  • If this is a bug, there are a concrete set of repro steps

Change

String literals are supposed in CEL are supposed to align with GoogleSQL. At present,
not all escape sequences are supported properly:

Issues

  • \xhh, \Xhh conversion of 2 hex chars to unicode code point.
  • \Uhhhhhhhh conversion of unicode escape with 8 hex chars supported incorrectly as \Uhhhh
  • r|R and b|B prefixes supported, but no support for rb for a raw byte string
  • Missing docs on standardizing all newlines to \n
  • Inconsistent treatment of standard escape patterns
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TristonianJones TristonianJones

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TristonianJones