Feature/add message binding to channel documentation#35
Conversation
✅ Deploy Preview for mellow-manatee-3041fb ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Great contribution! The data in the In terms of layout, I wonder if the items in example should be sorted the other way round. As an user, I am mostly interested in the payload/data, which I tend to expect first. What do you think? |
|
@stavshamir I'd like to motivate once more a common code formatting style. To me, it does not matter, which formatting is used, but it should be consistent. It also avoids the changed lines due to added/missing spaces. |
…dd header and message binding example to example tab
…he backend can use the message binding to construct a message
… creates a specification without message binding
… to log statement when producing messages
Regression: Previously included mapped ui attributes chore: Improve [protocol: string]: any typings Co-authored-by: david.mueller@codecentric.de
sam0r040
force-pushed
the
feature/add_message_binding_to_channel_documentation
branch
from
3ffd54e to
967a029
Compare
2 participants
This PR extends the springwolf-ui to display message binding information which is added in springwolf-core in springwolf/springwolf-core#130.
It also moves the editable header example to the example view so that everything that can be edited and send to the backend to produce messages is now on one screen.
Changes: