Export clscxt from facade
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, typescript
- Domain
- api
Research direction
Start at the package's facade entry point and inspect how the existing mdc, validator, and logger exports are assembled. Add clscxt to that public export list, then run the repository's available build or test command to confirm the facade exposes it.
Written by the indexing model from the issue text.
Description
export { mdc, validator, logger } from '@qiwi/mware'
export { default as clscxt } from '@qiwi/mware-context'
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from qiwi/mware
-
Dependency Dashboard Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
enhancement
-
Migrate to TS Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·