Skip to content

Conversation

@samuelstroschein
Copy link
Member

@samuelstroschein samuelstroschein commented Nov 23, 2025

Note

Fixes file observe invalidation to re-emit on state commits touching the same file, strengthens ProseMirror plugin (empty data, ID handling) with tests and example UI tweaks, and updates JSON/Markdown plugin READMEs.

  • SDK (observe)
    • Fix re-execution for file queries when state commits touch the same file_id (improves invalidation of file reads).
    • Enhance extractLiteralFilters to capture file_id and respect table aliases; refine schema-key detection; add targeted tests.
  • ProseMirror Plugin
    • applyChanges starts from an empty doc when file data is empty; remove legacy _id handling in schemas/diff logic.
    • Improve ordering/ID-based updates in applyChanges/detectChanges; expand test coverage.
    • Example app: add npm package link card; reset uses OpfsSahEnvironment.clear(); hide proposals tab; version toolbar adds "Merge to main" flow.
  • Docs
    • Overhaul READMEs for @lix-js/plugin-json, @lix-js/plugin-md, and @lix-js/plugin-prosemirror with install, quick start, and behavior details.
  • Flashtype UI
    • Minor JSX/UI tidy-ups in markdown rendering and code blocks.
  • Workspace
    • Exclude Next.js example apps from workspace.

Written by Cursor Bugbot for commit 48ed0de. This will update automatically on new commits. Configure here.

- Fix observe invalidation for file queries to prevent stale data.
- Update README for clarity and quick start instructions.
- Refactor code for better readability and maintainability.
- Add tests for observing file changes and extracting filters.
…improve clarity and consistency in descriptions.
@changeset-bot
Copy link

changeset-bot bot commented Nov 23, 2025

🦋 Changeset detected

Latest commit: 48ed0de

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "@inlang/paraglide-js-example-next-js-ssr" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@inlang/paraglide-js-example-next-js-ssg" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

@nx-cloud
Copy link

nx-cloud bot commented Nov 23, 2025

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci


View your CI Pipeline Execution ↗ for commit 48ed0de

Command Status Duration Result
nx run-many --nx-bail --target=build --parallel ✅ Succeeded 41s View ↗
nx run-many --target=test --parallel ✅ Succeeded 32s View ↗
nx run-many --target=lint --parallel ✅ Succeeded 2s View ↗

☁️ Nx Cloud last updated this comment at 2025-11-23 18:43:37 UTC

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ 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".

Comment on lines 260 to 264
for (const nodeId of childrenOrder) {
// First check if the node exists in the current document content
const existingNode = document.content.find(
(node) => (node.attrs?.id || node._id) === nodeId,
(node) => node.attrs?.id === nodeId,
);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Legacy ProseMirror nodes with _id are ignored

applyDocumentOrder now matches top-level nodes only by attrs.id, whereas previous versions (and the README that still mentions legacy _id support) accepted either attrs.id or _id. Existing documents persisted with _id but no attrs.id will no longer be found in the existing content or the node map, so rehydrating a file after this change will silently drop or reorder those nodes when changes are applied. Without a migration/normalization step, upgrading will lose content for any snapshots that relied on _id identifiers.

Useful? React with 👍 / 👎.

@samuelstroschein samuelstroschein temporarily deployed to add-plugin-md-readme - prosemirror-example PR #3761 November 23, 2025 03:29 — with Render Destroyed
…id columns as file_id

- Introduced a new test case for extractLiteralFilters to validate that joined id columns are correctly identified and not misclassified as file_id.
- Updated extractLiteralFilters function to handle table aliases and improve column reference extraction logic.
- Refactored table name extraction to support alias mapping for better accuracy in filter extraction.
@samuelstroschein samuelstroschein temporarily deployed to add-plugin-md-readme - lix-docs PR #3761 November 23, 2025 18:26 — with Render Destroyed
…pnpm-workspace.yaml to streamline package management.
@samuelstroschein samuelstroschein merged commit 8715dba into main Nov 23, 2025
3 checks passed
@samuelstroschein samuelstroschein deleted the add-plugin-md-readme branch November 23, 2025 18:49
@github-actions github-actions bot locked and limited conversation to collaborators Nov 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants