[feature/doc] Render results in a table
See original GitHub issueI know you can make awesome stuff when you are free to format the results from super awesome instant search. But how about traditional tables…?
Would be nice to have the ability to present the result in a plain table. (or at least some documentation for it)
Been playing around with it and even though I set the <ais-result> component to render as an tbody it just keeps on returning itself as a div and breaks the table formatting.
<tbody is="ais-results"> ... </tbody>
Still returns a div.
If we could just render the ais-results component as a tbody we would be all good.
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (12 by maintainers)
Top Results From Across the Web
Using material-table in React to build feature-rich data tables
A good table component should have the following features built in: Searching through data; Sorting data; Filtering columns; Download options ...
Read more >Rendering React Table [v7] results in [object Object]
I'm attempting to render a table of data inside a div and I'm unable to do so. Basically I just want to replace...
Read more >arcgis.features module | ArcGIS API for Python
If the operation is performed on a table, the result is a renderer object containing the data classes and no symbols. Argument. Description....
Read more >Motif Programming Manual (Volume 6A): 24 - Render Tables
This chapter describes the new features introduced in Motif 2.0 for rendering compound ... A Render table consists of a sequence of XmRendition...
Read more >Summarytools in R Markdown Documents
For a more in-depth view of the package's features, please see ... print(descr(tobacco), method = 'render', table.classes = 'st-small') ...
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
Here is a quick codepen that illustrates it: https://codepen.io/team/algolia/pen/qXRpzR?editors=1000
I’m also adding this to the docs in #257
I don’t think going for a “tag” is a good option as it will quickly add a lot of noise to the API. Indeed when using inline-templates, the scope is the one of the component you are inlining the template for, that is why you can no longer access your methods. This is also why it is not recommended to use inline-templates in the official docs.
If you need to go specific on the tags + the behavior, I would go for a custom component and extend the existing one. It is very simple to do so. Is there any reason you don’t want to go that route @techytuppers ?