Skip to content

feat: add parameter validation rules #4986

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.

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

robert-hebel-sb
Copy link
Contributor

Adds additional parameter validation rules

@robert-hebel-sb robert-hebel-sb added enhancement New feature or request ApiDOM TypeScript TypeScript related work labels Aug 6, 2025
marker: 'key',
markerTarget: 'name',
target: 'name',
data: {},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the empty data needed ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see it's a default in a case when we don't specify any quickfix rules

const filterSiblingsOAS3 = (el: Element) =>
isObject(el) && el.hasKey(key) && toValue(el.get(key)) === value;

const elements = filter((el) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the 'el' is any here right? can we do sth about it ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, I need to check why it's not picked up by eslint. Thanks for catching that. It's fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ApiDOM enhancement New feature or request TypeScript TypeScript related work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants