[BUG] The prop 'resourceName' of 'ListButton' does not take effect
See original GitHub issueDescribe the bug The prop ‘resourceName’ of ‘ListButton’ does not take effect
To Reproduce Use ‘ListButton’ with custom ‘resourceName’
Additional context
Look at the following codes
https://github.com/pankod/refine/blob/9b3fd9128228bc48eb0f75e0d524202daae3d7e2/packages/core/src/components/buttons/list/index.tsx#L46
https://github.com/pankod/refine/blob/9b3fd9128228bc48eb0f75e0d524202daae3d7e2/packages/core/src/components/buttons/list/index.tsx#L68
resourceName
is defined, but not used in the onClick
function.
Other buttons have similar problem too.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
[Bug] Using as prop on styled function component does not ...
[Bug] Using as prop on styled function component does not correctly inherit all styles # ... I have created a reproduction of the...
Read more >The List Component - React-admin - Marmelab
The default value for the component prop is Card . debounce. By default, <List> does not refresh the data as soon as the...
Read more >List - Refine Dev
The button text is defined automatically by refine based on resource object name property. Properties. resourceNameOrRouteName . Redirection ...
Read more >Visualforce in Practice - Salesforce Developers
This is not documentation, and it is not intended to document every feature built ... The code in Listing 3-3 is essentially creating...
Read more >Useful Patterns by Use Case - React TypeScript Cheatsheets
Usecase: you want to make a <Button> that takes all the normal props of <button> and ... {/* Error: Property 'toPrecision' does not...
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
Thanks for everything. May you have the best New Year ever~
Hey @wy-z , I’ve created a new PR. #1401. I hope it will merge next week after discussing it with the core team.