[Documentation] The changelog is not mentioning a breaking change.
See original GitHub issueDescription
TL;DR: The changelog is not mentioning a breaking change.
Before (I don’t know exactly when since the changelog do not talk about it) calling Swal()
was enough to launch the popup, now (I don’t know since when) Swal.fire()
is mandatory. The issue is that the Changelog don’t talk about that.
More information in the StackOverflow post.
Current behavior
Issue in the documentation not in the code!
Expected behavior
Issue in the documentation not in the code!
Live demo
Issue in the documentation not in the code!
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
documentation/CHANGELOG.md at master - GitHub
BREAKING CHANGES. nest: referencing inferred destructure params without renaming them, like $0.x, from JSDoc comments will no longer work. To reference them, ...
Read more >Keep a Changelog
Using commit log diffs as changelogs is a bad idea: they're full of noise. Things like merge commits, commits with obscure titles, documentation...
Read more >Changelog - npm Docs
Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see...
Read more >Changelog entries - GitLab Docs
See the complete list what comprises a GraphQL breaking change. Any change that introduces an ... Any experiment changes should not have a...
Read more >Breaking Changes on the HubSpot Platform
What changes qualify as breaking vs non-breaking. ... HubSpot API Docs. Discover APIs, integration guides, and other documentation. HubSpot Developer Docs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you @noraj and @gverni for the constructive discussion, the PR is merged now 👍
@noraj as I reported already in my comment, the breaking change for
Swal.fire()
is already in commit f581352 under title “BREAKING CHANGE: remove withNoNewKeyword enhancer”. I agree that this does not explicitly mention thefire()
method, but this can be seen inside the commit message.I let @limonte comment on the PR for the changelog. Keep in mind that the changelog is automatically generated using the commit title, and there is no commit with an explicit title referring to
Swal.fire()
. If we have to change the changelog, then I would rather add the link to the release note.