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.

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

Incorrect data type for exclusiveMinimum and exclusiveMaximum #96

Closed
ivanalayan15 opened this issue May 4, 2022 · 12 comments · Fixed by #99 or #100
Closed

Incorrect data type for exclusiveMinimum and exclusiveMaximum #96

ivanalayan15 opened this issue May 4, 2022 · 12 comments · Fixed by #99 or #100
Labels
bug Something isn't working

Comments

@ivanalayan15
Copy link

Describe the bug

Incorrect data type for exclusiveMinimum and exclusiveMaximum

How to Reproduce

See the Schema.java

exclusiveMinimum and exclusiveMaximum has a data type of integer which has to be a boolean.

Expected behavior

This fields should be boolean data type

@ivanalayan15 ivanalayan15 added the bug Something isn't working label May 4, 2022
@github-actions
Copy link

github-actions bot commented May 4, 2022

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@Crain-32
Copy link
Contributor

Crain-32 commented May 5, 2022

Numeric values are in line with the latest 2021 Draft

exclusiveMaximum/exclusiveMinimum were swapped from Boolean to Numeric around Draft-06, so no need for change.

@ivanalayan15
Copy link
Author

hmmm got it thanks for that, but should it be change to big decimal data type? to able to handle decimal values.

@Crain-32
Copy link
Contributor

Crain-32 commented May 6, 2022

Hmm, I didn't think about that. BigDecimal would put it into the greatest level of Compliance with the Draft, so probably that.

@Pakisan
Copy link
Member

Pakisan commented May 6, 2022

@Crain-32 @ivanalayan15 As I remember we must respect 07 standard. Will try to change it as soon as possible. Or you can crate pr

@Crain-32
Copy link
Contributor

Crain-32 commented May 6, 2022

@Pakisan You can find my Draft PR above. Kotlin wasn't working on my Local, so I made it in case someone else can run the tests while I debug Kotlin over the weekend.

Beyond exclusiveMin and exclusiveMax I swapped min and max to be BigDecimal, as the standard calls them "numbers".

Technically multipleOf could be a BigDecimal/BigInteger, however it states the value is only valid if Division by the value results in an integer. So I left it as-is.

@ivanalayan15
Copy link
Author

ivanalayan15 commented May 7, 2022

hi @Crain-32 @Pakisan , i raise a new PR since @Crain-32 changes when i test it on my local got some issue with unit test which broke because of the change of the data type here is the PR: #100 i able to run the kotlin test in my local see the pr for details thanks

@Crain-32
Copy link
Contributor

Crain-32 commented May 7, 2022

Once @Pakisan responds I can drop #99 and we can move forward with #100. Thanks for Testing that, I still need to fix my Kotlin :/

@ivanalayan15
Copy link
Author

hello @Pakisan any update on it thank you

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added stale and removed stale labels Sep 10, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jan 10, 2023
@Pakisan Pakisan removed the stale label Feb 15, 2023
@Pakisan
Copy link
Member

Pakisan commented Feb 15, 2023

@ivanalayan15 @Crain-32 merged.

#126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants