Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

exposes readBlob via lix client #3015

Closed
wants to merge 1 commit into from
Closed

exposes readBlob via lix client #3015

wants to merge 1 commit into from

Conversation

martin-lysk
Copy link
Contributor

This PR exposes a readBlob function to via lix client to allow to read a content of a blob via oid directly.

@martin-lysk martin-lysk requested a review from janfjohannes July 9, 2024 08:52
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jul 9, 2024

⚠️ No Changeset found

Latest commit: 7e8b610

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@samuelstroschein
Copy link
Member

Close because outdated? Lix is being re-build on sqlite

@github-actions github-actions bot locked and limited conversation to collaborators Aug 15, 2024
@samuelstroschein samuelstroschein deleted the martinlysk1/expose-readblob branch November 28, 2024 20:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@janfjohannes janfjohannes janfjohannes approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@martin-lysk @samuelstroschein @janfjohannes