Using custom values in Combobox causes "Maximum recursive updates exceeded" warning
See original GitHub issueWhat package within Headless UI are you using?
@headlessui/vue
What version of that package are you using?
v1.6.2
What browser are you using?
Firefox
Reproduction URL
Repo - fresh Vue/Vite app, just npm i && npm run dev
and open in a browser: https://github.com/bakerkretzmar/headless-ui-recursive-issue
Codesandbox: https://codesandbox.io/s/places-combobox-forked-2eyihf?file=/src/App.vue
Describe your issue
The Allowing custom values example from the docs produces several hundred console warnings from Vue that the maximum recursive updates have been exceeded.
Typing anything into the combobox produces about a hundred warnings immediately, and then hovering over each option in the list logs an additional error or two every time.
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:5 (1 by maintainers)
Top Results From Across the Web
I keep getting "maximum recursive updates exceeded" in Vue ...
Uncaught (in promise) Error: Maximum recursive updates exceeded. This means you have a reactive effect that is mutating its own dependencies ...
Read more >Maximum recursive updates exceeded when trying to render ...
Uncaught (in promise) Error: Maximum recursive updates exceeded. This means you have a reactive effect that is mutating its own dependencies ...
Read more >Maximum recursive updates exceeded in component - how to fix
I have a component with graphql query and takes in a search tag and a search query from another component. I am trying...
Read more >Defining SQL Queries Using View Objects - Oracle Help Center
This chapter explains how instances of entity-based view objects contained in the data model of your application module enable clients to search for,...
Read more >Databricks Utilities - Azure - Microsoft Learn
To list available utilities along with a short description for each utility, run dbutils.help() for Python or Scala. This example lists ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is a result of two things
:value="{ id: null, name: query }"
producing a new object every render and the internal active option tracking we do. We’re going to update the documentation to recommend acomputed()
property wrapping that value to work around this. I’ll leave this open until we’ve done that.Fantastic, thanks so much!