You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current capability design automatically pulls every capability file and resolves to the app runtime authority. While this is a good approach for developer experience, it is static and does not support more dynamic applications such as:
nightly releases including new features
feature-flag based multi application mode (for instance an admin vs user shared app that uses Cargo features to toggle what is compiled)
we should add an option to define capabilities in Rust code. Ideally this should still be done at compile time. Since the current capabilities resolution is done in the Context generation, we could extend it to allow defining capabilities conditionally:
#8797 implements the first step for this feature, without that change users need to define conditionally added capabilities in a separate folder otherwise they would be enabled automatically.
Alternatives considered
We could also allow defining the capability at runtime instead, but I'll open a separate issue for that one.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
The current capability design automatically pulls every capability file and resolves to the app runtime authority. While this is a good approach for developer experience, it is static and does not support more dynamic applications such as:
Describe the solution you'd like
we should add an option to define capabilities in Rust code. Ideally this should still be done at compile time. Since the current capabilities resolution is done in the Context generation, we could extend it to allow defining capabilities conditionally:
#8797 implements the first step for this feature, without that change users need to define conditionally added capabilities in a separate folder otherwise they would be enabled automatically.
Alternatives considered
We could also allow defining the capability at runtime instead, but I'll open a separate issue for that one.
Additional context
No response
The text was updated successfully, but these errors were encountered: