-
Notifications
You must be signed in to change notification settings - Fork 7
Jess/507 grantpermission form #539
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
Conversation
… interpretability
|
Also tested in solidpod DemoPod, add delete Permission form a Specific Resource working, but add/delete Permission from Any Resource giving an error. Suspected this might happen and will investigate. [ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: 'package:solidpod/src/solid/grant_permission_ui.dart': Failed assertion: line 304 pos 12: 'pdata != null': is not true. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks attractive - thanks @jesscmoore. Tested on NotePod. Noting above issues to be resolved - should we merge this and break the others out as separate issues to fix?
|
Noticed that the Demopod permission callback demo error relates to unchanged code. Tested this demo on dev branch, and discovered the permission callback demo error is a pre-existing error. Adding an issue for it. |
|
|
Thanks @jesscmoore Once the conflicts are resolved, do the merge! |
|
@gjwgit Resolved conflicts, updated changelog. This PR is ready for merging. Thanks for your quick reviews of the 3 PRs today. |

Pull Request Details
Merge after PRs for public/auth and success colors
What issue does this PR address
Associated Issue
Type of Change
How Has This Been Tested?
In notepad on macOS, select a note, click share icon, shared to individual and group recipients, revoked recipients.
Checklist
Complete the check-list below to ensure your branch is ready for PR.
make preporflutter analyze lib)dart testoutput or screenshot included in issue #Finalising
Once PR discussion is complete and reviewers have approved: