[17.0] web_m2x_options: raising "OwlError: Invalid props for component 'Many2ManyTagsAvatarUserField': unknown key 'searchLimit'"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start with the web_m2x_options field handling and compare how it passes props to Many2ManyTagsAvatarUserField; the error identifies searchLimit as the rejected key. Check the related issue #2934 for context. Done when opening a project_todo card in the 17.0 kanban view no longer raises this OwlError.
Written by the indexing model from the issue text.
Description
Module
web_m2x_options
Describe the bug and To Reproduce
Developer mode on. Go to project_todo app, kanban view, when clicking in a card the error arises. I think is just another manifestation of #2934.
17.0
Additional context
UncaughtPromiseError > OwlError
Uncaught Promise > Invalid props for component 'Many2ManyTagsAvatarUserField': unknown key 'searchLimit'
OwlError: Invalid props for component 'Many2ManyTagsAvatarUserField': unknown key 'searchLimit'
Error: Invalid props for component 'Many2ManyTagsAvatarUserField': unknown key 'searchLimit'
at Object.validateProps (http://localhost:17069/web/assets/debug/web.assets_web.js:10774:19) (/web/static/lib/owl/owl.js:3214)
at Field.template (eval at compile (http://localhost:17069/web/assets/debug/web.assets_web.js:13312:20), <anonymous>:17:13) (/web/static/lib/owl/owl.js:5752)
at Fiber._render (http://localhost:17069/web/assets/debug/web.assets_web.js:9343:38) (/web/static/lib/owl/owl.js:1783)
at Fiber.render (http://localhost:17069/web/assets/debug/web.assets_web.js:9335:18) (/web/static/lib/owl/owl.js:1775)
at ComponentNode.initiateRender (http://localhost:17069/web/assets/debug/web.assets_web.js:10015:23) (/web/static/lib/owl/owl.js:2455)
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 2.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OCA/web
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[19.0] web_timeline: ValueError "Invalid field 'date_start:month'" when grouping by a date fieldPossibly taken @stferraro claimed this today. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
[19.0] web_m2x_options: system parameter + m2o options not working properly when no recordsPossibly taken @CristhianAC claimed this 11 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
Migration to version 20.0Possibly taken A pull request linked to this issue is open or already merged. Openhelp wanted no stale work in progress
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
Similar issues
-
bug package:workers-shared
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/workers-sdk#16924 · 1 comment ·
Maintainers usually reply within 1 day
-
dashboard
Difficulty 2/5 Half a day Newbie friendliness 78/100
damodharg6/payledger#9 ·
-
parse: child keys like `007`, `1e3`, `0x1f`, `-1` make the parent an empty array and hide the valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/mobile area/ui good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
natemoo-re/ultrahtml#102 ·