fix: comment out status/registration console.warn in graphile-postgis #449
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
Comments out debug and status
console.warnstatements inPostgisRegisterTypesPlugin.tsthat were polluting test output and consumer logs.Changes:
graphile-postgis/src/PostgisRegisterTypesPlugin.ts:'PostGIS plugin enabled''Getting ${type.name} type...'debug info'Registering handler for ${GEOGRAPHY_TYPE.id}''Registering handler for ${GEOMETRY_TYPE.id}'Preserved (no changes):
Fixes constructive-io/projects-issues#409
Updates since last revision
Per feedback, changed approach from deleting console.warn statements to commenting them out. Restored files with legitimate warnings (those inside if statements) to their original state.
Review & Testing Checklist for Human
pnpm testingraphile-postgisto verify no regressionsTest plan: Run the graphile-postgis tests to confirm PostGIS functionality still works correctly.
Notes