-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
feat: use schema's title when available in {one,any,all}Of
applicators
#744
feat: use schema's title when available in {one,any,all}Of
applicators
#744
Conversation
{one,any,all}Of
applicators
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide 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.
Kudos, SonarCloud Quality Gate passed! |
{one,any,all}Of
applicators{one,any,all}Of
applicators
{one,any,all}Of
applicators{one,any,all}Of
applicators
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
/au |
@KtorZ would you mind merging the |
I'll try to get this done in the upcoming days! |
695ded8
to
c87fe54
Compare
@fmvilas done 👌 |
/au |
c87fe54
to
16a51de
Compare
no more long living release branches! sorry for any trouble with your PR 😞 but we really had to finally release this v1 and get rid of release branch maybe changing target branch from |
16a51de
to
1b1a754
Compare
No worries. Just switching the branch didn't do it (more than 100k lines changed for some reason). So I just pulled the latest master and cherry-picked the commit onto it. Seems like it's good. Let me know 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your patience. I left one small comment
Please also have a look at the linter issues
ERROR: (triple-equals) /home/runner/work/asyncapi-react/asyncapi-react/library/src/helpers/schema.ts[110, 27]: != should be !==
@KtorZ please fix linter issues and also update with latest master |
there is just one tiny fix
I cannot commit it directly for you as you open a PR not from personal but for organization fork |
Hello, @derberg! 👋🏼
|
I'll take care of it tomorrow 🫡 |
@KtorZ kind ping 😉 |
1b1a754
to
9cd9820
Compare
My bad. Tomorrow ended up being way further in the future than I anticipated. Linted + rebased on top of |
SonarCloud blocked merge because of new rule related to accessibility. Issue mitigated by creating #827 |
@KtorZ all looks good but sorry, cannot merge as I cannot update your branch on my own as it is an org-fork, you have to do it on your own again, sorry |
@KtorZ whenever you update your fork with latest master, just ping me directly here or in slack, so i will quickly merge |
Applicators can be a little hard to navigate, especially on deeply nested schema. While the uid provides a nice middleground solution, it doesn't actually work when schemas are defined outside of the main specification and more importantly, it isn't necessarily meant to be human-readable. The 'title' property however is meant just for that.
9cd9820
to
b3b48df
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@derberg 🙏 |
/rtm |
@KtorZ finally we did it 😄 |
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Easy enough ... 😶 |
yeah, organization forks are pain, at least for upstream maintainers 😃 |
otherCases: string, | ||
title?: string, | ||
) { | ||
const suffix = (title !== null && ` ${title}:`) || `:`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title can also be undefined
it seems. This introduced Consists of undefined:
for us. So this check needs to be improved.
Description
Applicators can be a little hard to navigate, especially on deeply nested schema. While the
uid
provides a nice middle-ground solution, it doesn't actually work when schemas are defined outside of the main specification and more importantly, it isn't necessarily meant to be human-readable. Thetitle
property however is meant just for that.Changes proposed in this pull request:
title
next to branches enumeration in{one,any,all}Of
applicators. When not available, it defaults to the current behavior.Related issue(s)
N/A