chore: release 4.2.2#534
Merged
Merged
Conversation
## Summary Migrates all screener endpoints from `/v1/quote/screener/*` to `/v1/quote/ai/screener/*` per [longbridge-terminal PR #217](longbridge/longbridge-terminal#217). ## Changes | Old endpoint | New endpoint | |---|---| | `GET /v1/quote/screener/strategies/recommend` | `GET /v1/quote/ai/screener/strategies/recommend` | | `GET /v1/quote/screener/strategies/mine` | `GET /v1/quote/ai/screener/strategies/mine` | | `GET /v1/quote/screener/strategy?id=N` | `GET /v1/quote/ai/screener/strategy/{id}` | | `POST /v1/quote/screener/search` | `POST /v1/quote/ai/screener/search` | | `GET /v1/quote/screener/indicators` | `GET /v1/quote/ai/screener/indicators` | ### Breaking changes - `screener_recommend_strategies(market)` and `screener_user_strategies(market)` now require a `market` parameter (Rust/Python/Node.js/Java/C) - `screener_strategy(id)` uses path param instead of query param 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
…532) ## Summary - The `/v1/quote/finance_calendar` endpoint paginates via a `next_date` cursor, but all SDK bindings were silently dropping it, making multi-page range queries return incomplete data (e.g. CRM.US, PDD.US, MRVL.US missing for a 2026-05-23→05-30 range) - `next_date` is now returned as-is in `CalendarEventsResponse` across all language SDKs so callers can follow the cursor themselves ## Changes | File | Change | |------|--------| | `rust/src/calendar/types.rs` | Add `next_date` to `CalendarEventsResponse` | | `rust/src/calendar/context.rs` | Revert to single request (no internal pagination) | | `c/src/calendar_context/types.rs` | Add `next_date` to C binding owned/FFI types | | `c/csrc/include/longbridge.h` | Add `next_date` to `lb_calendar_events_response_t` | | `cpp/include/calendar_context.hpp` | Add `next_date` to C++ `CalendarEventsResponse` struct | | `cpp/src/calendar_context.cpp` | Populate `next_date` from C response in callback | | `nodejs/index.d.ts` | Add `nextDate: string` to `CalendarEventsResponse` | | `python/pysrc/longbridge/openapi.pyi` | Add `next_date: str` to `CalendarEventsResponse` | | `java/.../CalendarEventsResponse.java` | Add `public String nextDate` | ## Related - Go SDK fix: longbridge/openapi-go#fix/finance-calendar-pagination - Issue: longbridge/developers#1045 (comment) --------- Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
## Summary Bump version to `4.2.2` and add CHANGELOG entry. ## Changes in 4.2.2 ### Fixed - **All languages:** `CalendarEventsResponse` now exposes `next_date` cursor — callers can pass it as `start` (with the same `end`) to fetch the next page of `/v1/quote/finance_calendar` results - **All languages:** `CalendarEventInfo.symbol` now returns standard symbol format (e.g. `CRM.US`) instead of raw `counter_id` format (e.g. `ST/US/CRM`) ## Related - PR #532
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Merge main into release to publish 4.2.2.
Changes in 4.2.2
Fixed
CalendarEventsResponsenow exposesnext_datecursor — callers can pass it asstart(with the sameend) to fetch the next page of/v1/quote/finance_calendarresultsCalendarEventInfo.symbolnow returns standard symbol format (e.g.CRM.US) instead of rawcounter_idformat (e.g.ST/US/CRM)