Skip to content

Conversation

@rishabh-gupta-hashicorp
Copy link
Contributor

Description

This PR upgrades Ember from v3.28 to v4.12
Along with Ember upgrade, the PR upgrades multiple other packages and fixes some more deprecations.
Multiple Code Refactoring and Linting changes to follow best practices for v4.12 as well as paves the way for version upgrade to v5.

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@github-actions github-actions bot added the theme/ui Anything related to the UI label Nov 20, 2025
@rishabh-gupta-hashicorp rishabh-gupta-hashicorp added the backport/all Apply backports for all active releases per .release/versions.hcl label Nov 20, 2025
@rishabh-gupta-hashicorp rishabh-gupta-hashicorp changed the title Rishabh gupta/UI/ember upgrade to v4.12 UI/ember upgrade to v4.12 Nov 24, 2025
"ember-data": "~3.28.6",
"ember-data-model-fragments": "5.0.0-beta.8",
"ember-data": "~4.0.0",
"ember-data-model-fragments": "6.0.10",
Copy link

@deanmarano deanmarano Nov 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would recommend matching ember-data-model-fragments 6.0.10 with ember-data 4.6.7 - that is the intended pairing.

@color='critical'
data-test-delete
{{on 'click' (fn confirm )}}
{{on 'click' confirm }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be this.confirm to reference the component. Also the same for the cancel below.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

confirm is trickling down as return value from the wrapping BlockSlot. It's not part of this object.

@color='critical'
@text='Delete'
{{on "click" (fn confirm )}}
{{on "click" confirm }}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be tied to the component action using this.

Suggested change
{{on "click" confirm }}
{{on "click" this.confirm }}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/all Apply backports for all active releases per .release/versions.hcl theme/ui Anything related to the UI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants