-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add a portal implementation #54
Conversation
7e128dd
to
d457d09
Compare
58572b4
to
140930d
Compare
74ee254
to
8d296e7
Compare
oo7-portal-impl/src/main.rs
Outdated
attributes, | ||
&secret, | ||
true, | ||
// TODO Find a better one. |
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.
is this what the current portal implementation doing?
eab6845
to
e40adc6
Compare
e40adc6
to
6ad53ed
Compare
This is something we can do later imho |
ed2745b
to
8e77eed
Compare
15e46a9
to
de47f50
Compare
b85d9c1
to
9fba035
Compare
b914433
to
8291639
Compare
Currently it still lacks: - Proper end-to-end tests on the CI using the support we have for the portal from the client side as well but that requires a mock server which we don't have an implementation for yet - Build system integration so that the necessary file for the binary to be picked up as a secret portal provider can be installed
8291639
to
0c74098
Compare
From my point of view, the only thing missing here is more testing. |
We can have more testing once we get the server bits re-implemented. Then we can write a mock implementation and have all the bits tested. For now, let us land it |
There are a few things missing
Request
doing the correct thing?This is compatible with gnome-keyring's stored secrets, but we store them with a more descriptive label, e.g.
See flatpak/xdg-desktop-portal#482.