A boilerplate including user authentication & authorization
Tech: Automerge, tRPC, Prisma and deployment on fly.io and vercel.com Bonus: includes explanation videos on the website
144 karma · joined November 1, 2012
https://twitter.com/nikgraf https://github.com/nikgraf
A boilerplate including user authentication & authorization
Tech: Automerge, tRPC, Prisma and deployment on fly.io and vercel.com Bonus: includes explanation videos on the website
Cosmos in my opinion is a fantastic tool and covers even some areas we haven't touch yet, but planning to do soon like injecting/manipulating the internal state of a component.
While there a many more differences these are probably the most interesting ones:
- The core of Carte blanche is a Webpack plugin. By hooking into the main compilation of Webpack Carte blanche can identify your components and list them in an application living within your running server on different URL path. The coolest part from my perspective is that we inherit all your webpack settings by default. No need to configure your loaders. Cosmos in comparison is a separate app.
- In Cosmos your need to write your examples by hand. Carte blanche reads out your propTypes/Flow types and allows us to generate a form input for each of your properties including nested structures like a person object containing an avatarUrl, firstName & lastName. This approach allowed us to create some kind of UI fuzz-testing feature in the interface. While I believe that it's important to focus your efforts designing/developing for the most likely cases it's also relevant to cover edge-cases. Fuzz-testing is a great way to discover them.
I hope this help. Let me know if you any other questions :)
Have you ever checked out: https://github.com/rackt/react-modal
Seems to be pretty solid implementation.
I don't know if inline-styles defined in JS are the end-game, but working with it in combination with building components turned out to be working way better for us than using CSS.
If you want to know more about it I highly recommend this slidedeck: https://speakerdeck.com/vjeux/react-css-in-js
Right now there is a lot of stuff happening to simulate Web Components. Going forward they will become a W3C Standard and we can reduce the complexity. You might want to look at the current Draft https://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/...
What’s happening at the moment is that the output for <x-loading></x-loading> is:
<span is="x-loading">
<style>
@-webkit-keyframes x-loading-dot {
0% {
opacity: 1;
}
50% {
opacity: 0;
}
100% {
opacity: 1;
}
}
.x-loading-one {
opacity: 1;
-webkit-animation: x-loading-dot 1.3s infinite;
-webkit-animation-delay: 0.0s;
}
.x-loading-two {
opacity: 1;
-webkit-animation: x-loading-dot 1.3s infinite;
-webkit-animation-delay: 0.2s;
}
.x-loading-three {
opacity: 1;
-webkit-animation: x-loading-dot 1.3s infinite;
-webkit-animation-delay: 0.3s;
}
</style>
<span class="q-x-loading" style="color: rgb(80, 80, 80);">
<span class="x-loading-one">.</span><span class="x-loading-two">.</span><span class="x-loading-three">.</span>
</span>
</span>
If a component like the overlay also contains logic the code will be added to your compiled and minified JavaScript output.For blossom.io/bee you can find the compiled output here https://www.blossom.io/bee_documentation.html_bootstrap.dart...
Universities do a great job teaching abstract concepts and doing research. Web became a great and wide spread platform. Sadly they often dictate students not to work with web-technologies. It's possible to teach the concepts and at the same time use state of the art technologies.
I believe there is plenty of room for improvments in universities. I would love to see distributed revision control systems as a standard for student projects.
It's great to see people like you challanging the status quo and try improve the environment.