Implement multiple .blocks files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 641
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 57
Description
Is it possible to implement several .blocks files? For example, to avoid cluttering one file with code blocks, as is done now?
I think this is needed for large projects, where it becomes difficult to find code blocks.
For example, you know Scratch, in which each sprite has its own code space. The problem is less exposed there.
For each file, a separate ts or py file would be created. And in .menubar .editortoggle .blocks-menuitem it would be possible to select the desired file from the dropdown menu.
How do you feel about such a proposal and is it possible to implement it?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing single-.blocks-file flow and the .menubar .editortoggle .blocks-menuitem entry point. Define how selecting a file maps to its separate ts or py file, then validate that large projects can switch among files without cluttering one code-block space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100