Skip to content

refactor(deploy): rename boolean functions with does/is prefix#3945

Open
Hassad674 wants to merge 1 commit intowasp-lang:mainfrom
Hassad674:refactor/deploy-function-naming
Open

refactor(deploy): rename boolean functions with does/is prefix#3945
Hassad674 wants to merge 1 commit intowasp-lang:mainfrom
Hassad674:refactor/deploy-function-naming

Conversation

@Hassad674
Copy link

Fixes #3422

Renamed boolean-returning functions in the deploy package to use does/is prefixes for clarity:

  • clientTomlExistsInProjectdoesClientTomlExistInProject
  • serverTomlExistsInProjectdoesServerTomlExistInProject
  • localTomlExistsdoesLocalTomlExist
  • flyctlExistsdoesFlyctlExist
  • secretExistsdoesSecretExist
  • buildDirExistsdoesBuildDirExist

All call sites updated. Mechanical change, no logic modifications.

  • I updated the tests
  • Update e2e tests
  • Update docs

Rename boolean-returning functions in the deploy package to follow
the does/is naming convention for better readability:

- clientTomlExistsInProject -> doesClientTomlExistInProject
- serverTomlExistsInProject -> doesServerTomlExistInProject
- localTomlExists -> doesLocalTomlExist
- flyctlExists -> doesFlyctlExist
- secretExists -> doesSecretExist
- buildDirExists -> doesBuildDirExist
@Hassad674 Hassad674 requested a review from a team as a code owner March 19, 2026 19:31
@Hassad674 Hassad674 requested review from FranjoMindek and removed request for a team March 19, 2026 19:31
@cprecioso
Copy link
Member

Hi @Hassad674, thanks for the contribution!

A couple of things before taking a look into this:

  • Can you please use the pull request template for the body description, and follow the instructions there?
  • Have you tried deploying a project locally with the changes you're proposing?
  • Is this PR mainly vibecoded? Do you personally understand the changes done and why they were proposed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clean up function names in the deploy package

2 participants