Be able to pass any kind of array to the Search component
See original GitHub issueSteps
results = [ {id: 1, title: 'title1', description: 'desc', bandName: 'maiden', genre: 'heavy metal'}, {id: 1, title: 'title1', description: 'desc', bandName: 'maiden', genre: 'heavy metal'} ]; <Search loading={isLoading} onSearchChange={this.handleSearchChange} results={results} value={value} resultRenderer={this.resultRenderer} />
Expected Result
This should not show any warnings
Actual Result
Displays this warning:
Warning: Failed prop type: Invalid prop
resultssupplied to
Search.
Version
0.68.3
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Passing array into URLSearchParams while consuming http ...
Going through the Angular documentation for URLSearchParams, I dint find any documentation on passing array as an parameter.
Read more >Arrays - Visual Basic | Microsoft Learn
By using an array, you can refer to these related values by the same name, and use a number that's called an index...
Read more >Arrays - Learn web development | MDN
In the final article of this module, we'll look at arrays — a neat way of storing a list of data items under...
Read more >Arrays in C++
An array is a collection of elements of the same type placed in contiguous memory locations that can be individually referenced by using...
Read more >5. Working with Arrays and Loops - JavaScript Cookbook [Book]
A for loop can be used to access every element of an array. The array begins at zero, and the array property length...
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 FreeTop 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
Top GitHub Comments
It looks that this issue can be solved by simplifying of prop’s validator, but it needs more attention.
Any solutions for this?