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.

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

Support unicode throughout #31

Merged
merged 14 commits into from
Oct 6, 2022
Merged

Support unicode throughout #31

merged 14 commits into from
Oct 6, 2022

Conversation

lukebakken
Copy link
Collaborator

@lukebakken lukebakken self-assigned this Sep 26, 2022
@lukebakken lukebakken added this to the 3.1.0 milestone Oct 5, 2022
@lukebakken lukebakken marked this pull request as ready for review October 5, 2022 19:00
@the-mikedavis the-mikedavis self-requested a review October 5, 2022 19:08
src/cuttlefish_generator.erl Show resolved Hide resolved
@michaelklishin michaelklishin merged commit 6b284f5 into master Oct 6, 2022
@michaelklishin michaelklishin deleted the lukebakken/unicode branch October 6, 2022 21:04
michaelklishin added a commit that referenced this pull request Aug 3, 2024
Currently Cuttlefish does not support string
values that include the # character.

This character is, however, used every so often
in generated passwords, identifiers and other
machine-produced values.

This PR introduces an alternative value
representation:

```
a.setting = 'sdkjf#hsdf$82836867#9237498'
```

which allows such values to be escaped using
single quotes. Single quotes are NOT
supported by these values by design,
I do not thing that the \' escaping would
be worth our time.

This also drops an invalid UTF-8 input
test that I could not get to work.
Somewhere inside Neotoma a returned error
has turned into an exception. Either way,
the limited validation for valid UTF-8 characters
is still in place.

Closes #37.

References #31.
lukebakken pushed a commit that referenced this pull request Aug 5, 2024
Currently Cuttlefish does not support string values that include the #
character.

This character is, however, used every so often in generated passwords,
identifiers and other machine-produced values.

This PR introduces an alternative value representation:

```
a.setting = 'sdkjf#hsdf$82836867#9237498'
```

...which allows such values to be escaped using single quotes. Single
quotes are NOT supported by these values by design, I do not thing that
the \' escaping would be worth our time.

This also drops an invalid UTF-8 input test that I could not get to
work. Somewhere inside Neotoma a returned error has turned into an
exception. Either way, the limited validation for valid UTF-8 characters
is still in place.

Closes #37.

References #31.

* Add an integration test for 'escaped values'
* One more test case for escaped values
* Fix `invalid_utf8_test` test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants