gnovm: add -X flag to gno run and gno test

[ygd58]

Adds a -X name=value flag (repeatable) to 'gno run' and 'gno test', mirroring 'go build -ldflags "-X pkg.name=value"'. Before parsing, matching package-level (unindented) 'var name = "..."' or 'var name string = "..."' declarations have their string literal initializer replaced with the given override value.

Note: 'gno build' and 'gno publish' do not currently exist as separate gno CLI subcommands (only run/test/lint/etc. do), so this covers the two existing commands that parse and execute .gno source directly.

Closes #1021

[Gno2D2]

🛠 PR Checks Summary

🔴 Pending initial approval by a review team member, or review from tech-staff

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• The pull request description provides enough details

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🔴 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: ygd58/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🔴 Requirement not satisfied
└── 🔴 If
    ├── 🔴 Condition
    │   └── 🔴 Or
    │       ├── 🔴 At least one of these user(s) reviewed the pull request: [aronpark1007 davd-gzl jefft0 notJoon omarsy MikaelVallenet] (with state "APPROVED")
    │       ├── 🔴 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🔴 Else
        └── 🔴 And
            ├── 🟢 This label is applied to pull request: review/triage-pending
            └── 🔴 On no pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)
    └── 🟢 Not (🔴 Pull request author is user: dependabot[bot])

Can be checked by

• team core-contributors

[notJoon]

I don't think using a regex is a good or safe approach, because it would replace not only the variable names but also all raw strings in the code.

the original issue requires support for build, test and publish but it doesn't look like all of those requirements have been addressed. so I think this is not acceptable in its current state

[ygd58]

Thanks for the review, both points are addressed:

1. Regex safety: rewrote patchXVars to use go/parser + go/printer instead of a text regex. It now walks only the parsed file's top-level Decls, so it can never match text inside a string literal (raw or otherwise) or a local variable in a function body -- only genuine package-level var name = "..." declarations (including grouped var (...) blocks) are eligible. Added a dedicated regression test for the exact raw-string scenario you described.

2. build/test/publish scope: gno build and gno publish do not currently exist as separate subcommands in the gno CLI (only run, test, lint, etc. do -- see gnovm/cmd/gno/main.go). This PR covers the two existing commands that parse and execute .gno source directly (run and test). If there's a different command I'm missing that should also support -X, happy to add it -- let me know which one you had in mind.