[DX] Add dev.yml scripts for opening editors#259
Open
kieran-osgood-shopify wants to merge 1 commit into
Open
Conversation
This was referenced Jun 5, 2026
Contributor
Author
38c7e69 to
9180e19
Compare
11 tasks
322ce6d to
96218ad
Compare
| module CheckoutKit | ||
| module CLI | ||
| module ConfigSummary | ||
| SENSITIVE_KEY_PATTERN = /(ACCESS_TOKEN|TOKEN|SECRET|PASSWORD|CHECKOUT_URL|MERCHANT_IDENTIFIER|SHOP_ID|ACCOUNT_ID|CLIENT_ID|AUTH|KEY)/i |
Contributor
Author
There was a problem hiding this comment.
Some shared verbose logging for --verbose when things go wrong
884e885 to
8583382
Compare
96218ad to
32f87fd
Compare
8583382 to
3e004af
Compare
32f87fd to
41300fd
Compare
dcf5776 to
a6a9cef
Compare
41300fd to
5174f36
Compare
5174f36 to
15fe32a
Compare
a6a9cef to
033b5cf
Compare
15fe32a to
d3f0978
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What changes are you making?
Introduces the following commands to streamline opening editors for the given platform
Adds a
.dev.envto allow customising the local dev experienceI'm thinking of ƒuture additions to this might will include the ability to configure the
USE_LOCAL_SDKoption for local dev against the libraries in react-nativeWe use this env file to set up a new var:
DEV_EDITOR- Select a command that exists in path, e.g.code,nvim,zedThis file is only for dev overrides and does not customise the library or demo apps.
Why
I considered
$EDITORor$VISUALbut these seem more suited to editing with command line utilities like gitI chose the
DEV_EDITORto simplify the mental overhead of supportPersonally I have
$EDITORset tonvimfor quick edits during git, but default to VSCode for the sample appsI wanted to avoid confusion in scripts that may rely on EDITOR being set, and rely on both
How to test
Setup a
.dev.envfile and override the DEV_EDITOR to your chosen editorcp .dev.env.example .dev.envBefore you merge
Important
platforms/swift/README.mdand/orplatforms/android/README.md)Releasing a new Swift version?
ShopifyCheckoutKit.podspecplatforms/swift/Sources/ShopifyCheckoutKit/ShopifyCheckoutKit.swiftplatforms/swift/CHANGELOG.mdplatforms/swift/README.md(major version only)Releasing a new Android version?
versionNameinplatforms/android/lib/build.gradleplatforms/android/CHANGELOG.mdplatforms/android/README.mdTip
See the Contributing documentation for the full release process per platform.