Skip to content

[Chore]: Update Ivy to 1.2.35 and migrate blades to IBladeContext#425

Open
ArtemLazarchuk wants to merge 11 commits intomainfrom
chore/update-ivy-version-1.2.35
Open

[Chore]: Update Ivy to 1.2.35 and migrate blades to IBladeContext#425
ArtemLazarchuk wants to merge 11 commits intomainfrom
chore/update-ivy-version-1.2.35

Conversation

@ArtemLazarchuk
Copy link
Copy Markdown
Collaborator

Summary

Bumps Ivy and Ivy.Analyser (where referenced) from 1.2.34 to 1.2.35 across multiple sample/demo projects.

API migration

Replaces blade resolution from UseContext<IBladeService>() with UseContext<IBladeContext>() to match the Ivy 1.2.35 API. Primary constructor parameters that previously took IBladeService are updated to IBladeContext where needed (e.g. nested views/helpers).

Scope (high level)

  • Agent demos (e.g. lovable-event-planner)
  • Package demos (closedxml, miniexcel, ollamasharp, etc.)
  • Project demos (showcase-crm, autodealer-crm, crm-vc, llm-tornado-*, sliplane-manage, microsoft-agent-framework, …) per individual commits

…lade context references for improved clarity
…5 and refactor blade context references for improved clarity
…odify blade context reference for improved clarity
…dize blade context references across multiple components for improved clarity
…ardize blade context references across multiple views for improved clarity
…odify blade context reference for improved clarity
…lade context references across multiple views for improved clarity
…dardize blade context references for improved clarity
@ArtemLazarchuk ArtemLazarchuk requested a review from rorychatt April 7, 2026 19:49
@ArtemLazarchuk ArtemLazarchuk self-assigned this Apr 7, 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