[sync] T4665 Fix link picker range selection after search#3224
[sync] T4665 Fix link picker range selection after search#3224tea-artist wants to merge 1 commit into
Conversation
Synced from teableio/teable-ee@f9d43ca Co-authored-by: Aries X <caoxing9@gmail.com> Co-authored-by: Bieber <artist@teable.io> Co-authored-by: Boris <boris2code@outlook.com> Co-authored-by: Jocky-Teable <jocky@teable.ai> Co-authored-by: Jun Lu <hammond@teable.io> Co-authored-by: Pengap <penganpingprivte@gmail.com> Co-authored-by: Uno <uno@teable.ai> Co-authored-by: nichenqin <nichenqin@hotmail.com>
|
|
1 similar comment
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: db69b981dc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| persistAttribution({ | ||
| ...storedAttribution?.value, | ||
| ...enrichAttribution(currentAttribution), |
There was a problem hiding this comment.
Reset stored UTM fields when a new touch is captured
If a user already has stored attribution and later lands with only a subset of parameters (for example just utm_source), this merge keeps stale keys from the previous campaign (such as an old utm_campaign) and only overwrites provided keys. That produces mixed, incorrect attribution payloads for analytics and downstream reporting; a new touch should replace prior campaign fields (while still re-enriching things like ga_client_id) instead of inheriting missing ones from storage.
Useful? React with 👍 / 👎.
| groupBy, | ||
| collapsedGroupIds, |
There was a problem hiding this comment.
Avoid sending un-serialized group query params to range-to-id
This now forwards groupBy and collapsedGroupIds into the range-to-id request, but getIdsFromRanges in packages/openapi/src/selection/range.ts only JSON-serializes filter, orderBy, and ranges. In grouped link-picker scenarios, these complex params are sent in raw Axios query format and can fail validation/parsing on the rangesToIdQuerySchema endpoint, causing range selection to break when grouping is active.
Useful? React with 👍 / 👎.
🧹 Preview Environment Cleanup
|
🔄 Automated sync from EE repository.
54 commit(s) synced since last sync.
Authors
Included commits
Latest source commit: teableio/teable-ee@f9d43ca
This PR was automatically created by the sync workflow.