-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ENH] add regeneration script for js library #4115
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
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8eb42a0
to
fc6c500
Compare
14ca0bb
to
e899a42
Compare
48d0344
to
e5513bc
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.
LGTM - can you bump the version in the package.json
fields so we can push a release?
fc4ab73
to
db274a6
Compare
ce1b2c1
to
3140593
Compare
b29f535
to
7a3f562
Compare
794ec4e
to
d0fc2ff
Compare
d0fc2ff
to
8af4235
Compare
Compaction assumes that enumeration position t_i means t_i was the last record seen and therefore next reader should read from t_i + 1. Log service was built and tested for t_i meaning t_i was the first record to return. Note: I changed the go code, but only by moving a +1 out a layer. The inner version was inconsistent with convention, so I updated it.
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.
One minor thing to look into
Do we need |
…chroma into jai/js-client-regen
Description of changes
This PR updates the regeneration script for the JS library to fix failing generation on the new openapi spec. It also overhauls the used functions, renaming the V2 references back to the normal references as per the openapi spec.
Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?