7 Matching Annotations
- May 2022
-
github.com github.com
-
'm open to considering adding this to core but it's such a rare need (given that you're the first to ever ask for it, and I've never wanted or needed an around(:all) hook) I have a preference for keeping it in external gem if we can do so w/o hooking into rspec's internals
-
- Nov 2020
-
github.com github.com
-
I thought about this while re-reviewing it and think it's probably not a good fit for the Yarn core because the use case is mainly for CI's. I believe that a simple shell script should fix most people's problems.
Tags
Annotators
URL
-
-
medium.com medium.com
-
If you are working in a large enterprise application, we have to create small components. Small components are much more flexible in terms of reusability and maintainability.
-
-
github.com github.com
-
This is Sass based, and therefore doesn't require Svelte components
Just because we could make Svelte wrapper components for each Material typography [thing], doesn't mean we should.
Compare:
material-ui [react] did make wrapper components for typography.
- But why did they? Is there a technical reason why they couldn't just do what svelte-material-ui did (as in, something technical that Svelte empowers/allows?), or did they just not consider it?
svelte-material-ui did not.
- And they were probably wise to not do so. Just reuse the existing work from the Material team so that there's less work for you to keep in sync and less chance of divergence.
-
- Oct 2020
-
final-form.org final-form.org
-
Doing a HOC properly, as a library should, with hoisted statics and displayName and ref, etc., is a hassle and would add unnecessary bulk.
-
-
-
And I'm all for not adding a gazillion flags to to an elegant library.
-
- Sep 2020
-
medium.com medium.com