Vendure connector: research GraphQL order and product boundary
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- graphql
- Domain
- backend-api-design, documentation
Research direction
Start with the official Vendure documentation for authentication, products, orders, stock, webhooks/events, and channels, as requested in the acceptance criteria. Document the mapping risks for variants, taxes, and channels, identify the first fixture to build, and confirm that no real store data or connector implementation is included.
Written by the indexing model from the issue text.
Description
Parent: #34
Problem
Vendure stores may be useful for open-source commerce users. Posnic needs a research issue before implementation.
Acceptance criteria
- Link official Vendure docs for auth, products, orders, stock, webhooks/events, and channels.
- Summarize the mapping risks for variants, taxes, and channels.
- Identify the first fixture a contributor should build.
- Use no real store data.
Out of scope
- Shipping a Vendure connector.
- Claiming compatibility on the website.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 516
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.
More from Posnic/POS
-
area: localization bug good first issue help wanted size: small
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-2 days Newbie friendliness 76/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area: ecommerce area: integrations documentation good first issue help wanted needs evidence size: small
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
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 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·