-
-
Notifications
You must be signed in to change notification settings - Fork 3k
feat(core): add capability devOnly
field
#13261
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
base: dev
Are you sure you want to change the base?
Conversation
a dev environment might need particular scope configurations (such as allowing a localhost API). This change allows marking a whole capability file as "dev only"
Package Changes Through 9ed7143There are 3 changes which include tauri-utils with minor, tauri-codegen with minor, tauri with minor Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
What about buildOnly/prodOnly (whatever you wanna call it)? |
the main idea of devOnly is that you could enable for instance connecting to a localhost server in dev mode only, not affecting the security scope of a prod app. I don't see value in the opposite - if you allow connecting to the real API backend for instance, that doesn't impact the security of the dev mode. |
How about just allowing to pass a capability from CLI, this way you can cover the dev only situation and potentially other environment specific capabilities The problem is all capabilities files are active by default and so we need to pair this with should a config option to select which capabilities file should be loaded |
Please correct me if I am wrong, can this not already be done by setting the devUrl in the |
i'm not sure how that's related to capabilities so i can't correct you 😅 The closest thing related to that is Lucas' |
I meant it as an alternative, but I see your point. 👍 |
a dev environment might need particular scope configurations (such as allowing a localhost API). This change allows marking a whole capability file as "dev only"