egoist/majo

Separate the majo instance and middleware context

Open

#12 opened on Jun 10, 2019

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (53 stars) (13 forks)user submission
:dollar: Funded on Issuehuntenhancementhelp wanted

Description

Some methods like stream.rename stream.createFile are only available in middlewares, if you call theme directly outside a middleware it will either not work or throw an error.

Backers (Total: $100.00)

Submitted pull Requests

Become a backer now!

Or submit a pull request to get the deposits!

Tips

Contributor guide

Tech stack
typescriptnodejs
Domain
backendtooling
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptNode.jsmiddleware pattern
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the MajoFiles class and middleware context in the source code (likely src/index.ts). Review the previously submitted pull requests (#16, #50, #52, #54) to understand attempted solutions and maintainer feedback. The goal is to distinguish methods that should be available on the main instance (like stream.rename) from those only relevant in middleware, and restructure accordingly.
Separate the majo instance and middleware context · egoist/majo#12 | Good First Issue