name attribute?Additional Questions:
I'm currently using a local project created with create-react-app to try the components and ran into this issue

Here's the code I was using and I might have forgotten something, but just in case someone can double check
import React, {useState} from 'react';
import ClayPagination from '@clayui/pagination';
import '@clayui/css/lib/css/atlas.css';
const spritemap = require('@clayui/css/lib/images/icons/icons.svg');
function App() {
const [active, setActive] = useState(1);
const totalPages = 100;
return (
<div id="app">
<ClayPagination
arial-label="pagination"
activePage={active}
onPageChange={setActive}
spritemap={spritemap}
totalPages={totalPages}
/>
</div>
);
}
export default App;
This one also needs support for extra attributes (it seemed that aria-label didn't get passed in my example) so I can send a PR for that
Yep, I guess all components should accept ...otherProps and render'em in the main (or more logic) element.
After speaking with @marcoscv @bryceosterhaus @diegonvs and @eduardoallegrini we think it might be better analysing each component to find a general pattern or at least a good way to support accesibility related attributes. So I'll won't send a PR just right now.
Publish #2608
Most helpful comment
Yep, I guess all components should accept
...otherPropsand render'em in the main (or more logic) element.