Repository navigation
fix(sheet): store the schema under bootgs-utils:schema, keep reading the old key - #567
Merged
Merged
Conversation
…the old key insertSchema writes the schema to developer metadata under bootgs-utils:schema. getSchema and removeSchema also accept the key used by apps-script-utils 2.x and older (apps-script-utils:schema), the current key winning when both exist, and insertSchema removes the old entry when it writes, so existing spreadsheets migrate on their own. LEGACY_SCHEMA_METADATA_KEYS lists the old keys. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stacked on #566 (base
docs/readme-i18n); GitHub retargets it todeveloponce #566 is merged.insertSchemastores a sheet's schema in developer metadata. With the move to@bootgs/utilsthe key changes fromapps-script-utils:schematobootgs-utils:schema, without breaking spreadsheets that already carry a schema:insertSchemawrites the new key and removes the old entry, so a spreadsheet migrates the next time its schema is written;getSchemareads both keys; when both exist, the new key wins;removeSchemaremoves both;LEGACY_SCHEMA_METADATA_KEYSlists the old keys (the check is inlined, so no new public function).Tests added: legacy schema is read, current key wins over legacy, legacy entry is removed by
removeSchema, andinsertSchemamigrates a legacy entry. Full suite 2538/2538, build, Prettier,docs:check.🤖 Generated with Claude Code