[sync] fix(v2): normalize link result lookups in base duplicate#3239
[sync] fix(v2): normalize link result lookups in base duplicate#3239tea-artist wants to merge 1 commit into
Conversation
Synced from teableio/teable-ee@b795e8b 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: ac3eacf05e
ℹ️ 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".
| views: table.views?.map((view) => ({ | ||
| id: view.id, | ||
| type: view.type, | ||
| name: view.name, | ||
| })), |
There was a problem hiding this comment.
Preserve full view config when duplicating base structure
The v2 duplicate path rebuilds each view with only id, type, and name, so exported view settings (for example filter/sort/group, column layout/meta, share settings, and lock state) are dropped when the new base is created. In DuplicateBaseHandler.createTables, those omitted properties are never forwarded to buildTableFromInput, which means duplicated bases can silently lose view behavior even though table/record data is copied.
Useful? React with 👍 / 👎.
🔄 Automated sync from EE repository.
68 commit(s) synced since last sync.
Authors
Included commits
Latest source commit: teableio/teable-ee@b795e8b
This PR was automatically created by the sync workflow.