Skip to content

feat(op): Deprecate framework-specific span ops - #622

Open
Lms24 wants to merge 2 commits into
lms/feat-op-deprecationfrom
lms/feat-deprecate-ui-framework-ops
Open

feat(op): Deprecate framework-specific span ops#622
Lms24 wants to merge 2 commits into
lms/feat-op-deprecationfrom
lms/feat-deprecate-ui-framework-ops

Conversation

@Lms24

@Lms24 Lms24 commented Sep 3, 2026

Copy link
Copy Markdown
Member

Description

Deprecates the framework specific ui.* and function.* ops. SDKs should use the framework agnostic ops instead. The constants are still generated, just marked as deprecated.

  • ui.react, ui.vue, ui.svelte become ui
  • ui.angular, ui.ember, ui.livewire become ui
  • ui.react.mount becomes ui.mount
  • ui.react.render becomes ui.render
  • ui.react.update becomes ui.update
  • function.nextjs, function.remix become function

Needs #621 to merge first.

PR Checklist

  • I have run yarn test and verified that the tests pass.
  • I have run yarn generate to generate and format code and docs.

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


New Features ✨

Attributes

  • Add sveltekit.* attributes emitted by SvelteKit's native spans by Lms24 in #611
  • Add browser.navigation.type, move navigation.* to router.navigation.* by logaretm in #600
  • Add langchain.chain.name (deprecated) in favor of gen_ai.pipeline.name by RulaKhaled in #599
  • Add browser.paint.type by Lms24 in #606

Names

  • Add FAAS function span name and description rules by Lms24 in #617
  • Add function span name and description rules by Lms24 in #618
  • Add browser.* span name and description rules by Lms24 in #607
  • Add cache span name rules by Lms24 in #605

Op

  • Deprecate framework-specific span ops by Lms24 in #622
  • Add span op deprecation support by Lms24 in #621

Other

  • (descriptions) Add graphql span description rules by Lms24 in #616

Bug Fixes 🐛

  • (descriptions) Add graphql-enhanced http.client span description template by Lms24 in #613

Internal Changes 🔧

Deps

  • Bump browserslist from 4.28.2 to 4.28.8 by dependabot in #614
  • Bump fast-uri from 3.1.5 to 3.1.7 by dependabot in #612

Other

  • (descriptions) Fix http.client span description example by Lms24 in #603
  • (names) Add OTel divergence note for graphql span names by Lms24 in #615

🤖 This preview updates automatically when you update the PR.

@Lms24
Lms24 force-pushed the lms/feat-deprecate-ui-framework-ops branch from 427d00e to beddc98 Compare September 3, 2026 13:00
@Lms24 Lms24 changed the title feat(op): Deprecate framework-specific ui.* span ops feat(op): Deprecate framework-specific span ops Sep 3, 2026
@Lms24
Lms24 marked this pull request as ready for review September 3, 2026 14:12
@Lms24
Lms24 requested review from a team, cleptric, mjq and nsdeschenes as code owners September 3, 2026 14:12
@Lms24 Lms24 self-assigned this Sep 3, 2026
Lms24 and others added 2 commits September 3, 2026 16:51
Deprecate the framework-specific UI ops (`ui.react`, `ui.react.mount`,
`ui.react.render`, `ui.react.update`, `ui.vue`, `ui.svelte`, `ui.angular`,
`ui.ember`, `ui.livewire`) in favour of the framework-agnostic `ui`, `ui.mount`,
`ui.render` and `ui.update` ops. Framework-specific ops split the same kind of
work across one op per framework, which makes the data harder to query and to
document.

The constants are still generated, now marked as deprecated for SDKs.

Refs GH-619
Co-Authored-By: Claude <noreply@anthropic.com>
Same rationale as the framework-specific `ui.*` ops: one op per framework splits
the same kind of work across several ops. Both are replaced by the generic
`function` op.

Refs GH-619
Co-Authored-By: Claude <noreply@anthropic.com>
@Lms24
Lms24 force-pushed the lms/feat-deprecate-ui-framework-ops branch from bdc19a4 to 4e22a89 Compare September 3, 2026 14:51
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.

2 participants