refactor: rename enableMetaApi to enableServicesApi #602
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.
Summary
Renames
enableMetaApitoenableServicesApiacross the codebase to better reflect the purpose of this option - it controls whether the services API (domain/subdomain routing viaservices_public) is enabled.Changes:
enableMetaApi→enableServicesApiinApiOptionsinterface (graphql/types)API_ENABLE_META→API_ENABLE_SERVICESenvironment variable (graphql/env)--metaApi→--servicesApiCLI flag (packages/cli)graphql/serverReview & Testing Checklist for Human
API_ENABLE_METAenv var orenableMetaApiconfig option are updated to use the new names--servicesApiflag works correctly:cnc server --no-servicesApishould prompt for schema selectionerrorOutputfield - this was a pre-existing change that needed syncing, not part of this renameTest plan:
cnc server --helpand verify--servicesApiappears in the help textcnc server --no-servicesApiand verify it prompts for schema selectionAPI_ENABLE_SERVICES=falseenv var and verify the server starts without services APINotes