Fix #2681: rename economicalSecurity to economicSecurity in schema - #3600
Open
Larslllllll wants to merge 1 commit into
Open
Fix #2681: rename economicalSecurity to economicSecurity in schema#3600Larslllllll wants to merge 1 commit into
Larslllllll wants to merge 1 commit into
Conversation
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
1 participant
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.
Fix #2681: rename economicalSecurity → economicSecurity in schema
Problem
economicalSecurityandeconomicalSecurityNotemisspell "economic security" — the standard term for a bridge or oracle's capital-at-stake / cost-to-corrupt guarantee. "Economical" means low-cost, an unrelated word. This affects all 219 bridges.csv and oracles.csv files (139 + 80).Fix
Renames both fields in the two places that define the canonical schema for bridges and oracles:
meta/columns.json: key, label for botheconomicSecurityandeconomicSecurityNotetools/schema.json: property definitions and required-field lists for both bridges and oracles schemasScope
Schema-only change. No CSV data files touched in this PR — those are covered separately in DBIP #2681's
main-branch companion PR (#3562), which is currently blocked on this schema update landing first.Why resubmit
A prior attempt (#3261) was auto-closed for 3+ days of inactivity, not for a technical defect — no CI checks ever ran against it. This PR reproduces the identical, verified-correct diff.
Fixes #2681 (schema half).