Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: ✨Provided barrier click disable functionality for a particular … #392

Merged
merged 1 commit into from
Feb 26, 2024

Conversation

jaiminrana05
Copy link
Contributor

…showcase (#387).

Description

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.

Related Issues

Closes #387

CHANGELOG.md Outdated
@@ -1,3 +1,6 @@
## [2.0.4]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please mention "unreleased" next to the version.

@@ -244,6 +244,9 @@ class Showcase extends StatefulWidget {
/// will still provide a callback.
final VoidCallback? onBarrierClick;

/// For disabling barrier interaction for a particular showCase
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please reword the documentation comment ?

"onTargetClick is required if you're using disposeOnTap");
"onTargetClick is required if you're using disposeOnTap"),
assert(onBarrierClick == null || disableBarrierInteraction == false,
"can't use both property at same time");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please include both properties' names instead of only mentioning "both" in the assert message.

"overlay opacity must be between 0 and 1.");
"overlay opacity must be between 0 and 1."),
assert(onBarrierClick == null || disableBarrierInteraction == false,
"can't use both property at same time");
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^^

@aditya-css aditya-css merged commit e9517c9 into master Feb 26, 2024
2 checks passed
@aditya-css aditya-css deleted the fix/issue_387_disable_barrier_click branch February 26, 2024 10:23
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.

Hi.thnaks for your perfect package.is it possible to disable barrier click?
2 participants