-
Notifications
You must be signed in to change notification settings - Fork 11
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
expose the rust cargo.toml version string #422
Conversation
We didn't get a chance to discuss the approach before implementation. Here are my thoughts:
|
Agreed on all counts. I was thinking about this too.
|
The method definition can be the same as other FFI methods
|
That makes a lot of sense. Let's go with what you described. Is there a reason to return the full version in addition to the major and minor numbers? I think we should just return the version string and leave it at that. Definitely have the metadata map though. |
Because it's simple to do so, and wrapper may make decisions based on different major versions, but not care about minor or patch changes for example. |
That does make a good deal of sense. Since we aren't really releasing patch versions of the okapi binaries much, that should be enough. |
These are only available at compile-time, so custom requesting of the information is not possible. |
Java Test Report12 files ±0 12 suites ±0 2s ⏱️ ±0s Results for commit 2971477. ± Comparison against base commit 7a35aef. This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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.
Can you do cargo fmt
? It seems there's a file that needs formatting.
5c1371f
to
2971477
Compare
I will handle rubocop and flake8 code style issues in a separate PR. |
No description provided.