-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: enforcing API consistency (also across FFI) #49
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
returning a String was weird!
so now it creates a table on the fly and the thing that lua receives behaves like you would expect instead of being weird!
Co-authored-by: zaaarf <[email protected]>
zaaarf
added
core
This issue is related to the core Rust library
tweak
Code quality
labels
Oct 15, 2024
This was referenced Oct 15, 2024
…s and fetch_buffers Co-authored-by: alemi <[email protected]>
Co-authored-by: alemi <[email protected]>
ghyatzo
requested changes
Oct 16, 2024
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 reviewed the changes, also the python part. The config constructor signature was incorrectly changed (unless there was a reason for it?) so that should be reverted.
I've left some comments where I had some doubts.
<3
zaaarf
changed the title
chore: enforcing API consistency across FFI
chore: enforcing API consistency (also across FFI)
Oct 16, 2024
alemidev
previously approved these changes
Oct 16, 2024
frelodev
requested changes
Oct 16, 2024
Co-authored-by: frelodev <[email protected]>
…nd password as mandatory.
frelodev
approved these changes
Oct 16, 2024
ghyatzo
approved these changes
Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To make development easier, so far we've been lax enough with naming and typing.
In an effort to make the API more consistent across languages (and to amend some questionable naming choices) we're doing a round of mass renaming. And, in some cases, of adding stuff that probably should've been there and bugfixing (especially in the realm of inconsistent method signatures).
Honorable mentions: the method formerly known as
list_buffer_users
, who was implemented correctly in the glue a grand total of 1 time (JavaScript, gg @frelodev).Feel free to add any fixes if we missed anything.