logseq / logseq/db-test

purge this 100M limit on assets

Open
#1,143 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

This is app used mostly by computer people. Why would you tell me how big my assets are supposed to be. I would love to use DB version, but I cannot even import my previous graph because of this. Just remove this limit. just add a dialog reminding of big asset issues and thats it. Instead, you are making Tim Cook design choices.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the 100M asset-size limit and the DB-version graph import path described in the issue. Confirm where the size check is applied and how the proposed warning dialog would fit; done means oversized assets can be imported without the hard block while users receive the requested warning.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.