Open defuncart opened 4 months ago
@ueman Thanks for creating this package :) Please review API and let me know what you think. Once API is approved, appropriate tests can be added.
Hey, thanks for the contribution. The API seems perfectly fine for me. Thanks for working on it.
Attention: Patch coverage is 96.29630%
with 1 lines
in your changes are missing coverage. Please review.
Project coverage is 83.77%. Comparing base (
471cc7b
) to head (df234c7
). Report is 3 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
feedback/lib/src/feedback_widget.dart | 66.66% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:scroll: Description
Adds the option to define
supportedModes
so that, for instance,FeedbackMode.navigate
is not displayed.:bulb: Motivation and Context
For a single page desktop application, the
navigate
option may not be required. Moreover, the user can continue to interact with the application as usual (i.e. right click), thus there can be cases where we do not want to allow the user to interact while the feedback window is open.Conversely, I am not sure if there are real-world use-cases where the user can interact/navigate but not draw, nevertheless those would be covered by this PR.
:green_heart: How did you test it?
Update
example/lib/main.dart
, changesupportedModes
accordingly.Technically the user can select
which is non-sensical. A check in
FeedbackWidget
ensures correct state, however the api could be updated, i.e. first value ofsupportedModes
.Moreover, assets/errors could be raised when
supportedModes
is empty;:pencil: Checklist
:crystal_ball: Next steps
FeedbackMode.navigate
perhaps needs a renaming tointeractive
. This, perhaps, could be more descriptive. Such a change, however, would be a breaking change best suited to another PR.mode
was left as-is to not introduce any breaking changes (see discussion above).