-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ElsaDashboard javascript issue after migrating from 2.13 to 2.14 #4847
Comments
I also encountered the same problem, any help? |
@SipkeSchoorstraRTL any idea? |
Seems to be related to emileber/axios-middleware#62 simply put, emileber/axios-middleware doesn't work with Axios ≥ 1 as |
Might be a good idea to automate UI testing for early discovery. |
My bad, I overlooked this while making the release. I think the reason is this PR 3e16e6a. I will try to reverse it by selecting a compatible axios version < 1.2.0 and make a fix release. |
Should be fixed with 2.14.1 https://github.com/elsa-workflows/elsa-core/releases/tag/2.14.1 |
Hi, thank you very much for your quick reaction and fix. |
Hello,
I just migrated from Elsa 2.13 to 2.14.
It has solved compilation warnings due to migration to .NET 8, thank you.
However, there is an issue now with loading the dashboard on the client-side:
p-e37496bc.js:2 Uncaught (in promise) TypeError: r.originalAdapter.call is not a function
at e (p-e37496bc.js:2:897)
at async Object.list (p-04c30d61.js:1:4811)
at async se.componentWillLoad (p-23353c0b.entry.js:1:21264)
The text was updated successfully, but these errors were encountered: