-
Notifications
You must be signed in to change notification settings - Fork 15
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
Number of fixes (typos, error names unification) #184
Conversation
b928ecc
to
543ce01
Compare
142624f
to
c717aa4
Compare
README.md
Outdated
@@ -66,7 +66,7 @@ local result, err = crud.insert_object(space_name, object, opts) | |||
|
|||
where: | |||
|
|||
* `space_name` (`string`) - name of the space to insert an object | |||
* `space_name` (`string|number`) - name or numerical id of the space to insert an object |
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.
Is it tested anyhow?
Won't it be a problem because on different replicasets the same space could have different id?
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.
No actually, I have reverted these changes.
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 see no problems here. LGTM.
Should not we include the error naming change into the changelog? It is the user visible thing.
Please, update the CHANGELOG. |
We use `errors.new_class()` that declares error names. Error names usually has a form "<OperationName>Error", but some error codes has a form "<OperationName>". This patch makes all error names conform to the first form.
@mRrvz Updated. |
PLEASE MERGE IT WITH REBASE (without squash)
What has been done? Why? What problem is being solved?
I didn't forget about
Closes #???