core spec version 0.9.4, component.schema.name pattern is not accepting person names
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- yaml
- Domain
- api
Research direction
Start at core/v0/api/core.yaml around line 1918 and inspect the pattern defined for component.schema.name. Confirm the intended valid person-name examples and check how the schema validates them. Done means the schema accepts valid names such as “steve” and “john” without breaking the surrounding format.
Written by the indexing model from the issue text.
Description
Describe the bug
there is a pattern set for component.schema.name, it is 'pattern: ^./[^/]+/[^/]/[^/]/[^/]/[^/]/[^/]*$'
this pattern is not accepting the commonly used names. we tried with simple name, i,e, "steve", "john" etc. its still not accepting these name.
Defined here
https://github.com/beckn/protocol-specifications/blob/core-0.9.4/core/v0/api/core.yaml#L1918
Expected behavior
It should expect any valid person name
- Dominant language
- No language data
- Stars
- 453
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 beckn/protocol-specifications
-
Migrate default branch from `master` to `main`May be free again @ravi-prakash-v claimed this 369 days ago, and no pull request is open. Openworking group meeting
beckn/protocol-specifications#491 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
beckn/protocol-specifications#472 · 3 comments ·
-
Restructure spec repos to allow more interactive learning of the specMay be free again @rajaneeshk90 claimed this 713 days ago, and no pull request is open. Openprotocol-specifications
beckn/protocol-specifications#455 · 1 assignee ·
-
Design specifications for Open Data platformMay be free again @rajaneeshk90 claimed this 713 days ago, and no pull request is open. Openprotocol-specifications
beckn/protocol-specifications#454 · 1 assignee ·
-
Protocol-Specification Version 1.2 releaseMay be free again @rajaneeshk90 claimed this 713 days ago, and no pull request is open. Openprotocol-specifications
beckn/protocol-specifications#451 · 2 comments · 1 assignee ·
All issues in beckn/protocol-specifications
Similar issues
-
bug severity:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
semantic-release/gitlab#1032 ·
-
(config)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
suitenumerique/conversations#757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day