Conversation
… on request - renamedFrom / dropped Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Renders specification proposal IntentFile/intent-specification#96 (
0060) on the site: a new section renamedFrom / dropped - evolving a table that already holds data indocs/spec/entities.md(after unique - a business key over more than one field), arenamedFromrow in the fields key table, adropped:row in the entity-level attributes table, and two rows indocs/reference.md.renamedFrom: <old field name>- applying the file renames the stored column in place, so the values move with the new name; it acts only while the old column exists and the new one does not, so it is harmless to leave in the file after the rename ran.dropped: [names]- former field / to-one relation names whose columns applying the file removes, data included (the explicit contract step of expand/contract).::: info Normative: a field simply deleted from the file keeps its column and values; the authoring errors (adropped:name orrenamedFrom:source the entity still declares - by column -, a self-rename, a source also underdropped:, two fields renamed from one name, an empty name).Wording mirrors the proposal's specification text, one heading level shallower.
npm run docs:buildis green; the built HTML carriesid="renamedfrom-dropped-evolving-a-table-that-already-holds-data"and both new links (chapter tables, reference) resolve to it.Reference implementation: eclipse-dirigible/dirigible#7674.
🤖 Generated with Claude Code