Skip to content

docs: note that @currentEnv can reference an imported flag - #1067

Merged
theoephraim merged 1 commit into
mainfrom
docs-imported-currentenv-note
Sep 4, 2026
Merged

docs: note that @currentEnv can reference an imported flag#1067
theoephraim merged 1 commit into
mainfrom
docs-imported-currentenv-note

Conversation

@theoephraim

Copy link
Copy Markdown
Member

Follow-up to #1066. The environments guide still implied the @currentEnv flag item had to be defined in the same file; it can now come in via @import.

Original change by @WalksWithASwagger, split out of #1062.

Follow-up to #1066: the environments guide still said the flag had to live
in the same file.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
varlock-website f42fa32 Commit Preview URL

Branch Preview URL
Sep 04 2026, 03:52 AM

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes Documentation clarification for imported @currentEnv flags.

  • Environment flag source Clarifies that the item referenced by @currentEnv may be defined locally or supplied through @import, consistent with the implementation, tests, import guide, and root-decorator reference.

Pullfrog  | View workflow run | Using azure/gpt-5.6-sol𝕏

@theoephraim
theoephraim merged commit d6043af into main Sep 4, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants