-
Notifications
You must be signed in to change notification settings - Fork 35
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
Using the responsive option cause an Internal Error: too much recursion #125
Comments
If anyone is interested, I found a workaround.. not the best, obviously, but it solves my problem. I'm using Here is what I do: import { breakpointsTailwind, useBreakpoints } from "@vueuse/core";
const breakpoints = useBreakpoints(breakpointsTailwind);
const isSmall = breakpoints.smaller("lg");
const options: Ref<ApexOptions> = computed(() => ({
legend: {
position: isSmall.value ? "bottom" : "right",
fontSize: isSmall.value ? "18px" : "20px",
},
})); instead of:
|
I've also bumped into this... the issue seems to start as long as I update other |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I do think that this issue still applies dear 🤖 |
As soon as I add a
responsive
property in theconfig
object, any update to the config will trigger a "too much recursion" error.I found a similar report on StackOverflow
Reproduction
I created a simple bug reproduction there.
1️⃣ Once loaded, go to page A. You should see the chart.
2️⃣ Click on "back" home.
3️⃣ Go to page B. You don't see the chart.
In the console you should see the error:
Uncaught (in promise) InternalError: too much recursion
.If you click on "back" home, you won't be able to.. and the console display the error:
Uncaught (in promise) TypeError: this.w.globals.dom.Paper is undefined
.Refreshing the page solves the issue, but this is not the intended behavior.
If we don't set the
responsive
property on theconfig
, then, none of those error would happen.The text was updated successfully, but these errors were encountered: