chore(sdk): Add pageParams and query to initUVE
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
User Story
The initUVE function should receive both the page parameters (pageParams) and the GraphQL query (query) at initialization time.
The goal is to enable UVE to replicate the exact same request made by the client application, ensuring both UVE and the app return consistent results.
This payload should match the structure used by the client.get.page() function in the new SDK
Acceptance Criteria
The initUVE function must accept all pageParams and the GraphQL query supported by client.get.page().
Proposed Objective
Technical User Experience
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating initUVE in the new SDK and compare its current inputs with the payload accepted by client.get.page(). Trace how pageParams and query are represented and passed through initialization. Done means initUVE accepts the same supported page parameters and GraphQL query, with tests confirming UVE can reproduce the client request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100