Chance Strickland

I think this is an area we might want to solicit feedback from the community. Here are two approaches that I *think* could work pretty well: - We have a...

I do like it, but might it increase the scope of the project a bit for an initial feature? Personally I'd rather nail the core behavior related to axe first...

Yeah, it'd be nice to experiment with other tools and see about making them pluggable. Personally I think axe is the best tool of its kind and others will have...

Yeah, I haven't vetted the idea thoroughly so it's possible there are some gaps. I want to explore it a bit more before adding to the conversation. As far as...

I think it could be useful to do both. Or better yet, perhaps, what if the component name linked directly to open up a tab in React Dev Tools if...

@mick-feller Have you tried the dynamic import syntax? https://reactjs.org/docs/code-splitting.html#import? This is untested, but I *think* it should look something like this: ```js const reqSvgs = require.context('./svgdir', true, /\.svg$/); reqSvgs.keys().map((filename) =>...

I honestly hadn't considered that I'd get PRs for this, but now I have to think about it 😂 Ok, new rule: I have to try the recipe first, but...

Hey @Volker-E, if this is still of interest to you, I forked this as a new side-project and am using WPCS to ensure compliance with WordPress-VIP standards (as well as...

Having not been around when this was designed in v5, I can't speak to _why_, but the `component` prop expects a component that takes a `navigate` prop instead of simply...

I know this is not ideal, and we'll figure out a better workaround, but I spun up a quick example of a custom `Link` implementation that should work in the...