docs: end OAuth Flows Object field descriptions always with dot

[char0n]

Some fixed fields description have dots and some don't. This PR provides remediation and introduces a little bit more consistency.

[smoya]

LGTM, however I think docs: commit prefix fits better than refactor:.

[char0n]

LGTM, however I think docs: commit prefix fits better than refactor:.

Sure, can be address by squash and merge workflow, or do you want me to force push a new amended commit msg?

[smoya]

LGTM, however I think docs: commit prefix fits better than refactor:.

Sure, can be address by squash and merge workflow, or do you want me to force push a new amended commit msg?

You just need to change it in the PR title. The PR title is used as the commit message when squashing.

[char0n]

Done.

[fmvilas]

Looks good to me too.

@derberg is our CI aware of things like docs(asyncapi.md): in the PR title? Or should we just use docs: or chore:?

[derberg]

it should be just docs: and then it will automatically be refreshed on the website

this is editorial change, why not against master? it doesn't change the meaning

[char0n]

this is editorial change, why not against master? it doesn't change the meaning

I'm not familiar with all the internal rules of the AsyncAPI org. My intention was to increase the quality of the spec and from time to time I'm reviewing main README file and CONTRIBUTING to find directional information about current processes. From these two documents I haven't found a guideline, against what to actually send a PR, so I've send it to the same branch I was asked to send it the last time.

[derberg]

@char0n no worries, happy to explain.

The only difference is that if you make an editorial change against next-major, then the change will wait until the next release window to get released. And if the change is introduced against master, and with docs: prefix, then we update it also automatically on asyncapi.com

so yeah, editorial changes is a key here, because if it is more, then yeah, should not go to master

The base branch was changed.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[char0n]

Base branch changed, thanks for explanation.

[derberg]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 2.5.0-next-major-spec.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[fmvilas]

Forget about the last comment saying it was released in version 2.5.0-next-major-spec.1. I made a mistake and it created this version but it should actually be 3.0.0-next-major-spec.1. There's a notice in the release. Apologies for the noise.

[asyncapi-bot]

🎉 This PR is included in version 2.5.0-next-spec.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[derberg]

Recent comments about the release from the bot were added by mistake. More details in #899