Add a Python-independent Rust API for file and notebook editing - #49
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move structured command parsing, file-qualified addresses, notebook cell resolution, views, and write orchestration into the Rust core. Python APIs and CLIs now delegate to this shared implementation, and PyO3 is optional.
Preserve notebook source representation and unrelated metadata, including arbitrary-precision JSON numbers. Add Rust regression coverage for file transfers, failed edits, and notebook preservation.
See DEV.md’s “Hash verification timing” and “Command parsing modes” for execution and write semantics.