refactor: rename renameMap to schemaRenameMap for clarity #274
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
renameMaptoschemaRenameMapthroughout the schema rename test to make it explicit that this map is specifically for schema renaming. This prepares for future extensibility where other rename maps (for tables, functions, triggers, etc.) may be added.Changes:
RenameMapinterface →SchemaRenameMaprenameMapvariable →schemaRenameMapin all function parameters and usagesrenameMapSummary→schemaRenameMapSummaryrename-maptoschema-rename-mapReview & Testing Checklist for Human
renameMapreferences were missed (search forrenameMapin the test file)Test plan: Run
pnpm testinpackages/plpgsql-deparser- all 58 tests and 28 snapshots should pass.Notes