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

fix: ensure string auto fields can be generated #21

Merged
merged 2 commits into from
Jul 23, 2022

Conversation

mikefero
Copy link
Contributor

This fixes an issue where the value for an auto generate string is either ngx.null or nil which have two different meaning in goks as OpenResty is not used.

This fixes an issue where the value for an auto generate string is
either ngx.null or nil which have two different meaning in goks
as OpenResty is not used.
@mikefero mikefero requested a review from a team as a code owner July 22, 2022 21:11
@hbagdi
Copy link
Member

hbagdi commented Jul 22, 2022

Can we add a test for this?

GGabriele
GGabriele previously approved these changes Jul 23, 2022
@mikefero
Copy link
Contributor Author

Added a test; once approved the entire PR can be squashed and a new version of goks can be generated.

To make validation easier for ngx.now, the golang ngx.now package has
separated out the function that processes the Lua function.
Copy link
Contributor

@GGabriele GGabriele left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great.

Apologies, I didn't think about this when I worked on the other PR :(

@mikefero mikefero merged commit 80d0c11 into main Jul 23, 2022
@mikefero mikefero deleted the fix/string-auto-field branch July 23, 2022 23:35
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