Release/26.6.1#136
Conversation
…ion-in-get-api SK-2658 add all query params available in get
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
skyflow-bharti
force-pushed
the
release/26.6.1
branch
from
acf1090 to
c7a79cb
Compare
|
✅ Gitleaks Findings: No secrets detected. Safe to proceed! |
|
Semgrep findings: No issues found, Good to merge. |
3 participants
SK-2658 — Add column/field selection support to get() API
Problem
The get() method did not support field-level filtering, making it incompatible with column-scoped vault policies. When a role only has access to a subset of columns, a get() call that fetches all columns returns a 403. Customers like PrizePicks need to pre-fill forms using only the permitted fields (e.g. occupation, annual_income) while excluding sensitive ones (e.g. ssn).
Additionally, the REST API supports several query parameters (fields, offset, limit, downloadURL, order_by) that had no SDK equivalent.
Changes
IGetOptions — Extended with all missing REST API query parameters:
downloadURL?: boolean — request pre-signed download URLs
orderBy?: OrderBy — result ordering (ASCENDING | DESCENDING | NONE)
IGetRecord — Extended with all missing REST API query parameters:
fields?: string[] — column filter; maps to ?fields=col1&fields=col2
offset?: string — pagination start
limit?: string — pagination page size