question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Documentation] The changelog is not mentioning a breaking change.

See original GitHub issue

Description

See https://stackoverflow.com/questions/56416187/sweetalert2-typeerror-this-is-undefined-after-v8-upgrade/

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:closed
  • Created 4 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
limontecommented, Jun 3, 2019

Thank you @noraj and @gverni for the constructive discussion, the PR is merged now 👍

1reaction
gvernicommented, Jun 2, 2019

Are in the CHANGELOG.md but not Breaking change # 1 - swal(…) -> Swal.fire(…)

@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 the fire() 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.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found