-
-
Notifications
You must be signed in to change notification settings - Fork 128
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: render bindings in relevant sections #259
Conversation
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.
Great! Thanks for contribution! I will also make review for this part with rendering in new way the messages/payloads
section. Probably we should introduce these changes in followup issue/PR.
Hi, |
Co-authored-by: Maciej Urbańczyk <[email protected]>
@195858 Very good, but I have some problems with modified part related to messages/operations: Could you fix styling (paddings) for header title here? In addition, make that the badge I don't know from which part we have this blank content, but it should be removed. Do you wanna to render the summary and description in toggle? If this is intentional, I would prefer to do this in followup PR and modify other parts including channels, schematic etc, because currently we have inconsistencies. In addition, as you can see, the styles don't look very good :) |
<section | ||
className={bemClasses.element(`${className}-oneOf-${payloadType}`)} | ||
> | ||
<header | ||
className={bemClasses.element( | ||
`${className}-oneOf-${payloadType}-header`, | ||
)} | ||
> | ||
<h3> | ||
{isPublish && isSubscribe ? ( | ||
<Badge | ||
type={ | ||
payloadType === PayloadType.PUBLISH | ||
? BadgeType.PUBLISH | ||
: BadgeType.SUBSCRIBE | ||
} | ||
/> | ||
) : null} | ||
<span> | ||
{payloadType === PayloadType.PUBLISH | ||
? ONE_OF_FOLLOWING_MESSAGES_PUBLISH_SINGLE_TEXT | ||
: ONE_OF_FOLLOWING_MESSAGES_SUBSCRIBE_SINGLE_TEXT} | ||
</span> | ||
</h3> | ||
</header> | ||
{operation.summary && ( | ||
<div className={bemClasses.element(`${className}-description`)}> | ||
<Markdown>{operation.summary}</Markdown> | ||
</div> | ||
)} |
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.
Why do you wanna render single message with styling for oneOf
?
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.
I simply reused the existing styles - I think the action to take here is to create separate styles.
I just wanted the message to be rendered similar to one-of because the previous rendering omitted information. If a channel had both subscribe
and publish
operations the result was really confusing.
Hence I added the help text and the summary if it exists.
Will do.
It's because the message does have neither a description nor a summary.
OK, the toggle was there before - however I see that the description is now presented in the collapsed view. I'll address this |
A further remark - summary was rendered as part fo the header before. I don;t think I changed it - however I'll clean it up/find a better looking way. |
@195858 Thank you very much for your work! I appreciate that. Please ping me when you done :) |
@magicmatatjahu - made some changes ... The channel operation has a new header format. Operation binding and messages section is now indented so it's easier to see how the sections relate. |
@195858 Thanks for patience and for your work! I wanted to see it in my local machine, but as I see, styles aren't update from 14 days. Do you could push changes for new styling described in your last comment? I like the styles very much :) |
Kudos, SonarCloud Quality Gate passed! |
@magicmatatjahu - sorry forgot to push my changes. |
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! :) Thanks for contribution!
@195858 I forgot that non-maintainers hasn't access to merge... Very, very sorry for delay and thanks again for contribution! |
🎉 This PR is included in version 0.21.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@all-contributors please add @195858 for code |
I've put up a pull request to add @195858! 🎉 |
Description
Changes proposed in this pull request: