-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
doc-gen: migrate scalar functions (string) documentation 1/4 #13924
doc-gen: migrate scalar functions (string) documentation 1/4 #13924
Conversation
I believe you may have forgotten to run the doc generation script prior to pushing this change |
@Omega359 Yes 😢 I'll run doc generation script for other PRs all together. Thanks for reviewing 🙏 |
```sql | ||
trim(trim_str FROM str) | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@comphead I found that use_doc()
only supports one alternative syntax. Should we modify it to support multiple alternative syntaxes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh its a vec, yeah we should do it, as well as simplify a little bit the Documentation
structure to replace Option<Vec>
to just Vec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets leave trim not migrated for now and we can do it once the doc macros fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remove the change for trim()
in this PR, thanks! I'd like to update use_doc()
and migrate trim()
simultaneously
dcda1b8
to
bd8033e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @Chen-Yuan-Lai lgtm
Which issue does this PR close?
Part of #13671 .
Rationale for this change
What changes are included in this PR?
As discussed in #13671 , this PR will migrate the parts of builtin string functions documentation that currently support migration.
Are these changes tested?
Are there any user-facing changes?