Wrap unique() in double quotes to better indicate that it's a literal… #2600
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… string
What does this PR do?
In the documentation, many endpoints allow the string
"unique()"
to be used to indicate that a random uuid should be generated. Currently, the documentation displays"unique()"
as plain text.This can mislead readers (like myself), to think that there is a function
unique()
to generate a uuid on the client side. The current approach in the documentation uses single ` signs aroundunique
to indicate a code block, but it does not get rendered in the actual docs.The proposed fix, wrapping
unique()
in double quotes, is a temporary fix to clearly indicate that it's a string. A more permanent fix would be to fix the rendering of inline code snippets in the docs.https://appwrite.io/docs/server/functions
Related PRs and Issues
None that I know of
Have you read the [Contributing Guidelines on issues]
Yes :D