Skip to content

Conversation

hashicc
Copy link
Collaborator

@hashicc hashicc commented Sep 30, 2025

Description

This adds a patch for ember-loading dependency since it uses older ember-concurrency versions and supporting addons which prevent us from using vite-compatible addons. Patching the dependency's package.json doesn't actually change what gets installed so the manual overrides to ember-concurrency v4 is also needed.

How to Test

  1. Add a is-loading: {{is-loading}} to the application.hbs in desktop or admin
  2. Add a server.timing = 1000 to the mirage scenario or use the app with a real api
  3. Launch the app and navigate around, any loading requests should trigger is-loading: true in the browser and then when the loading is finished the is-loading: false should be shown

Checklist

  • I have added before and after screenshots for UI changes
  • I have added JSON response output for API changes
  • I have added steps to reproduce and test for bug fixes in the description
  • I have commented on my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have added a11y-tests label to run a11y audit tests if needed

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.

Copy link

vercel bot commented Sep 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
boundary-ui Ready Ready Preview Comment Oct 7, 2025 2:19pm
boundary-ui-desktop Ready Ready Preview Comment Oct 7, 2025 2:19pm

@@ -0,0 +1,112 @@
diff --git a/addon/services/loading.ts b/addon/services/loading.ts
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Comment on lines +84 to +93
module.exports = {
name: require('./package').name,
+ options: {
+ babel: {
+ plugins: [
+ require.resolve('ember-concurrency/async-arrow-task-transform'),
+ ],
+ },
+ },
};
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

"ember-try-config>package-json": "^10.0.1",
"ember-stargate@^0.6.0>@glimmer/component": "^2.0.0"
"ember-stargate@^0.6.0>@glimmer/component": "^2.0.0",
"ember-loading>ember-concurrency": "^4.0.0"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this needed? It looks like you changed the ember-loading package.json to instead make ember-concurrency a peer dep, would it not just load our app's version now?

Copy link
Collaborator Author

@hashicc hashicc Oct 6, 2025

Choose a reason for hiding this comment

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

Patching the dependency's package.json doesn't actually change what gets installed so the manual overrides to ember-concurrency v4 is also needed.

I treated the patch as what the package output should be, but unfortunately the way the patches are resolved don't impact how the dependencies are managed and stored in the lockfile. Aside from changing the version I wanted to hint at that ember-concurrency-async and ember-concurrency-ts shouldn't be used, but those are also in the lockfile still. If this is more confusing than helpful I can remove the dependency changes from the package.json patch

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

Successfully merging this pull request may close these issues.

2 participants