Skip to content

Label the dot-path document update as eppy compatibility - #37

Merged
samuelduchesne merged 1 commit into
mainfrom
015-object-multi-field-update
Oct 21, 2026
Merged

samuelduchesne merged 1 commit into
mainfrom
015-object-multi-field-update

Conversation

@samuelduchesne

Copy link
Copy Markdown
Contributor

Summary

The migration guide's "Batch updates" section presented IDFDocument.update({"Zone.Office.x_origin": 10.0}) as idfkit's own way to edit several fields. That method is part of the eppy compatibility surface, which the naming register excludes. This change:

  • relabels that example as eppy compatibility;
  • adds the native form after it: fetch the object once and assign its fields (docs/snippets/migration/batch_updates_3.py);
  • in the comparison table, shows the native form in the "idfkit" column and keeps doc.update(d) in the "eppy alias in idfkit?" column, with the footnote updated to match.

No other prose is changed. When IDFObject.update ships (idfkit/idfkit#235), the native form will be revised to use it.

Checks

  • make check: passed, including the type check of the new snippet.
  • make docs-test: the strict build reports 113 warnings locally, all of them cairosvg failing to load the system cairo library for social cards. Excluding those, the build reports no warnings, and the migration page renders both snippets.

The "Batch updates" section presented IDFDocument.update, which takes
"Type.Name.field" keys, as idfkit's own way to edit several fields. It is
part of the excluded eppy compatibility surface. The section now says so
and follows it with the native form, which fetches the object once and
assigns its fields. The comparison table shows the native form in the
idfkit column and keeps doc.update(d) in the eppy alias column.

idfkit-unification feature 015, FR-016.
@github-actions

Copy link
Copy Markdown
Contributor

Docs preview for this PR is available at:
https://developers.idfkit.com/pr-preview/pr-37/

Changed pages:

github-actions Bot added a commit that referenced this pull request Oct 21, 2026
@samuelduchesne
samuelduchesne merged commit d220f28 into main Oct 21, 2026
7 checks passed
github-actions Bot added a commit that referenced this pull request Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant