This will give you complete intellisense and type safety within your app and CSS modules
🚨 NOTE
- refactoring className from ts file wont update your css/scss className, to change class names you have to change it within your
.module.scssfile
This is the first post of a series about Algebraic Effects and Handlers.
There are 2 ways to approach this topic:
Both approaches are valuables and give different insights on the topic. However, not everyone (including me), has the prerequisites to grasp the concepts of Category theory and Abstract Algebra. On the other hand, the operational approach is accessible to a much wider audience of programmers even if it doesn't provide the full picture.
Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.
The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from
| import Html exposing (..) | |
| import Keyboard | |
| import Window exposing (Size) | |
| import AnimationFrame | |
| import Task | |
| import Html.App as App | |
| import Collage exposing (..) | |
| import Element exposing (..) |
| // Define your components like: | |
| class MyComponent extends React.Component { | |
| static fetchData = (params) => { | |
| // return an action here. | |
| }; | |
| /* ... */ | |
| } | |
| function fetchComponentData(component, store, params) { |
In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.
At the moment GraphQL allows 2 types of queries:
querymutationReference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
| #!/usr/bin/env ruby | |
| # This script has been slightly adapted from: | |
| # http://blog.bigbinary.com/2013/09/19/do-not-allow-force-pusht-to-master.html | |
| class PrePushHandler | |
| def handle | |
| reject if force_pushing? && pushing_to_master? | |
| end |