| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <script src="./react-0.13.3.min.js"></script> | |
| <script src="./browser.min.js"></script> | |
| </head> | |
| <body> | |
| <div id="mount"></div> | |
| </body> |
| # Creates a private BitBucket repository with one call from bash | |
| # -------------------------------------------------------------------------------- | |
| # | |
| # Uses the BitBucket REST API to create a new private, non-forkable repository | |
| # for the local Git repository your currently staying in. | |
| # The content of your local repository gets pushed after the repository is created. | |
| # | |
| # Prequisites: | |
| # - you must have curl installed | |
| # - your local repo must not have a remote already connect to a bitbucket repo |
| import React from 'react'; | |
| import ReactDOM from 'react-dom'; | |
| class Input extends React.Component { | |
| constructor() { | |
| super(); | |
| this.state = { | |
| greeting: '' | |
| } | |
| } |
| function getEventTarget(nativeEvent) { | |
| var target = nativeEvent.target || nativeEvent.srcElement || window; | |
| // If encapsulated in a Web Component | |
| // use the Event path | |
| if(nativeEvent.path && nativeEvent.path[0]) { | |
| return nativeEvent.path[0]; | |
| } | |
| // Normalize SVG <use> element events #4963 |
| class Hello { | |
| async greet() { | |
| return new Promise(res => { | |
| setTimeout(() => res("Hallo Welt"), 1000); | |
| }); | |
| } | |
| } | |
| const hello = new Hello(); | |
| (async () => { |
If you're developing an application based on React it can be helpful if you don't need to develop all the basic UI components yourself. Here you can find a list with various components, component libraries and complete design systems developed with and for React.
As the list got longer and longer I thought it would be better to have a "real" site for it.
| import * as React from "react"; | |
| import * as ReactDOM from "react-dom"; | |
| import { ApolloClient } from "apollo-client"; | |
| import { HttpLink } from "apollo-link-http"; | |
| import { InMemoryCache } from "apollo-cache-inmemory"; | |
| import { ApolloProvider, withApollo } from "react-apollo"; | |
| const apolloClient = new ApolloClient({ |
Currently when using apollo-codegen to generate TypeScript types for query definitions (ts-modern target),
the generated types are called as the query name. So if you have a GetUserQuery your basetype is called GetUserQuery.
But in fact the type does not desribe the actual query, but the outcome, the result of the query, so it would be better
if the type would have been named like UserQueryResult.
There is an issue in apollo-codegen where this issue is discussed: apollographql/apollo-tooling#315
But as there is currently no progress I wrote a little codemod (using jscodeshift)
that renames the types after they have been generated. You can find the transform.js script below.
The GitHub GraphQL API Ankündigung und Begründung für die GitHub GraphQL API
https://developer.github.com/v4/guides/ - Allgemeine GraphQL API Doku von Github
Mutations in der GitHi API Hier seht ihr zumindest, wie die API aussieht (leider keine Begründung, warum sie so aussieht)
GraphQL Best Practices - leider recht abstrakt
Pagination - Paginierung in GraphQL. Mein Tipp ist, dass man in der Regel sich die Sache vereinfachen kann, wenn man statt eines Cursors eine "gewohnte" Seiten-basierte Paginierung verwendet. Trotzdem ist der Artikel eine gute Inspiration.
Öffentliche GraphQL APIs - Eine Liste mit öffentlichen GraphQL APIs, hier könnt ihr Euch "inspirieren" lassen
[Mein Talk](https://n