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

Look at using a different capability name for a modifiable key store #398

Open
darranl opened this issue Feb 4, 2017 · 0 comments
Open
Milestone

Comments

@darranl
Copy link
Contributor

darranl commented Feb 4, 2017

We currently have a special interface which can return a modifiable variant.

Is this really necessary or could we just use a different capability name and where a resource type supports modifiable register as two capabilities.

@darranl darranl modified the milestones: 1.0.0.Beta7, 1.0.0.Beta8, 1.0.0.Beta9, 1.0.0.Beta10 Feb 14, 2017
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

No branches or pull requests

1 participant