Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Rule: Strings and Numbers should have correct validations #16

Closed
5 tasks done
mnaumanali94 opened this issue Nov 16, 2022 · 2 comments
Closed
5 tasks done

New Rule: Strings and Numbers should have correct validations #16

mnaumanali94 opened this issue Nov 16, 2022 · 2 comments
Labels
released

Comments

@mnaumanali94
Copy link
Collaborator

mnaumanali94 commented Nov 16, 2022 •
edited by philsturgeon

User Story Description

As an API designer I want to be sure that I'm securing my API by precisely defining the types, and patterns you will accept in requests at design time.

Acceptance Criteria

  • Define min/max length for integer
  • Define format for integer
  • Define max length for string
  • Define pattern for string
  • Severity: Error

More information: https://apisecurity.io/encyclopedia/content/owasp/api7-security-misconfiguration
philsturgeon added a commit that referenced this issue Nov 16, 2022
@philsturgeon
feat: array size and string size
cfabd60 
part of #16
@philsturgeon
Copy link
Contributor

@mnaumanali94 Think I've got this done, could you give it a thumb if it looks good and tested enough?

@github-actions
Copy link

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philsturgeon @mnaumanali94