Skip to content

Conversation

Flamingloon
Copy link

@Flamingloon Flamingloon commented Sep 23, 2025

Description

Currently we can provide both title and text null which should not be the case so to prevent this added assertion

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
  • I have followed the Contributor Guide when preparing my PR.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples or docs.

Breaking Change?

  • Yes, this PR is a breaking change.
  • No, this PR is not a breaking change.

current behaviour:

image

@Flamingloon Flamingloon changed the title !chore: πŸ‘¨β€πŸ’»Add assertion for title and description both can't be null chore!: πŸ‘¨β€πŸ’»Add assertion for title and description both can't be null Sep 23, 2025
@Flamingloon Flamingloon changed the title chore!: πŸ‘¨β€πŸ’»Add assertion for title and description both can't be null chore!: πŸ‘¨β€πŸ’» Add assertion for title and description both can't be null Sep 23, 2025
@Sahil-Simform Sahil-Simform force-pushed the fix/assertion_for_null_description_and_title branch from ec70a78 to 0566832 Compare September 23, 2025 17:34
@aditya-css
Copy link
Collaborator

This has already been accommodated in PR #570. Thanks for contributing!

@aditya-css aditya-css closed this Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants