suggestly_flutter 0.4.0
suggestly_flutter: ^0.4.0 copied to clipboard
Themeable dialogs in flutter for Suggestly feedback flows: feature requests, bug reports, and ratings.
Changelog #
All notable changes to this project will be documented in this file.
0.4.0 - 2025-11-14 #
- Simplified
Suggestly.ensureSubmissionIdentityso it only ensures the Suggestly user exists and mints a submission token; reviewer onboarding is now handled automatically by the backend once feedback is submitted. ThepresentationContextparameter has been removed and the SDK no longer prompts for or caches reviewer invite tokens. - Deleted the reviewer invite prompt/store implementation along with the
shared_preferencesdependency and its associated widget tests/documentation. - Updated the README, demo client, and widget suite to describe the new reviewer email invite flow that runs after submissions instead of during identity creation.
0.3.1 - 2025-11-13 #
- Added optional
reviewerInviteTokenplumbing toSuggestly.ensureSubmissionIdentity,_SuggestlyClient, the README, example host app, and widget tests so private applications can hand reviewer invites to their early users. When provided, the token is forwarded to/public/users/ensure-token, and refreshed identities reuse the lightweight/public/users/tokenendpoint with the existingSuggestlyPublicheader. - The Flutter demo now surfaces a field for invite tokens and passes them through to the backend.
0.3.0 - 2025-11-13 #
- Breaking: Feature request, bug report, and rating popups (and the
Suggestly.submit*helpers) now require aSubmissionIdentityinstead of a bareuserId. Replace calls toSuggestly.ensureUserExists/Suggestly.userExistswith the newSuggestly.ensureSubmissionIdentityhelper so each session mints a signed submission token alongside the canonical user ID. - All eligibility checks and submissions now include the signed token via
SuggestlyPublicheaders, with automatic caching/refresh logic and optional TTL/nonce overrides to keep identities active without re-prompting users. - Updated the README, demo client, tests, and example host app to reflect the new identity flow and keep profile fetch/update plumbing internal to the Flutter package.
0.2.2 - 2025-11-12 #
- Incremented the package version to prepare the next Suggestly Flutter release.
0.2.1 - 2025-10-30 #
- Prefixed the feature request, bug report, and rating popups with
Suggestlyto avoid collisions when integrating alongside other packages. - Updated the example app, documentation, and widget tests to reflect the renamed popups.
0.2.0 - 2025-10-29 #
- Breaking:
SuggestlyFeatureRequestPopup.show,SuggestlyBugReportPopup.show, andSuggestlyRatingPopup.shownow returnSuggestlyPopupResult<FeedbackSubmissionResult>instead ofbool?, exposing whether the dialog appeared, the submission outcome, and any error data. Update call sites to inspectdidSubmit,wasShown, andhasError. - Added the new
SuggestlyPopupResulttype (exported fromsuggestly_flutter.dart) so popups return the backendFeedbackSubmissionResulton success and structured error details on failure. - Permission and eligibility failures short-circuit with
SuggestlyPopupResult.error, ensuring host apps can surface meaningful messaging even when the dialog never renders. - Popups remember the most recent error when cancelled, allowing hosts to surface
errorMessagewhen users back out after a failure. - Fixed the eligibility checker to call
/public/access, matching the deployed Suggestly API route and restoring feedback permission lookups. - Introduced an
example/Flutter host app for manual testing with either the built-in demo client or a live Suggestly API key.
0.1.7 - 2025-10-29 #
- Restored the trailing slash on the default API base URL so relative paths keep the
/apiprefix when resolved, matching Firebase Cloud Functions routing. - Clarified the URI resolution logic to avoid regressions when targeting self-hosted Suggestly deployments.
0.1.6 - 2025-10-29 #
- Fixed the client URI resolver so requests keep the
/apiprefix when hitting self-hosted Suggestly deployments, preventing 404s during initialisation.
0.1.5 - 2025-10-28 #
- Removed the need to supply email or name when submitting bug reports, feature requests, or ratings; the backend now resolves those details using only the Suggestly
userId. - Dialogs continue to prompt for a missing display name and update the user profile before submitting feedback, ensuring newly entered names persist.
0.1.4 - 2025-10-28 #
Suggestly.initializeis now asynchronous and validates the provided API key against the Suggestly API before activating the client; invalid credentials throwSuggestlyApiException.- Collaborators can now submit ratings while an application remains in Draft, and the popups surface a draft-only notice alongside new automated tests.
0.1.3 - 2025-10-24 #
- Increased default input padding so floating labels no longer clip when fields are focused or filled.
- Ensured the alignment fix applies consistently across bug report, feature request, and rating popups.
0.1.2 - 2025-10-24 #
- Refreshed README to reflect built-in screenshot picking, correct package path, and the streamlined Suggestly client API.
- Removed references to the deprecated
TextInputPopupworkflow from the documentation. - Clarified bug report attachment limits and file validation in the documentation.
0.1.1 - 2025-10-23 #
- Bug report popup now owns screenshot selection using
file_selector, removing the host-providedonAddAttachmentscallback. - Added attachment validation and deterministic fallback filenames so backend uploads work reliably.
- Simplified
Suggestly.initialize/SuggestlyClientpublic API to only require an API key and added testing hooks for overriding the client. - Fixed missing immutability annotations and refreshed widget tests to match the new attachment flow.
0.1.0 - 2025-10-23 #
- Initial release of
suggestly_flutterproviding Material 3 dialogs for Suggestly workflows. - Includes text input, feature request, bug report (with attachments), and rating popups.
- Adds theming helpers, typed responses, and integration tests covering the dialogs.