All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
| val (recycleQueue, recycleSource) = | |
| Source | |
| .queue[SoilStateReading](100, OverflowStrategy.dropTail) | |
| .prefixAndTail(0) | |
| .map(_._2) | |
| .toMat(Sink.head)(Keep.both) | |
| .run() | |
| StreamConverters.fromInputStream(() => this.getClass.getClassLoader.getResourceAsStream("sensors.log")) | |
| .via(SoilStateReading.csvParser) | |
| .merge(Source.fromFutureSource(recycleSource)) |
| import akka.stream._ | |
| import akka.stream.scaladsl._ | |
| /*** | |
| * Example based on numBuckets = 3 | |
| * --- bucket 1 flow --- ~mapAsync(parallelism)~ --- | |
| * |------------------| / \|---------------| | |
| * Open inlet[A] --- | Partition Fan Out| --- bucket 2 flow --- ~mapAsync(parallelism)~ -----| Merge Fan In | --- Open outlet[B] | |
| * |------------------| \ /|---------------| | |
| * --- bucket 3 flow --- ~mapAsync(parallelism)~ --- | |
| * |
| // getComponent is a function that returns a promise for a component | |
| // It will not be called until the first mount | |
| function asyncComponent(getComponent) { | |
| return class AsyncComponent extends React.Component { | |
| static Component = null; | |
| state = { Component: AsyncComponent.Component }; | |
| componentWillMount() { | |
| if (!this.state.Component) { | |
| getComponent().then(Component => { |
| class frugal1_estimator(object): | |
| def __init__(self, qtile): | |
| self.qtile_target = qtile | |
| self.m = 0.0 | |
| def add(self, new_data): | |
| r = random.random() | |
| if new_data > self.m and r > (1.0 - self.qtile_target): | |
| self.m += 1 | |
| elif new_data < self.m and r > self.qtile_target: |
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
I was trying to understand JavaScript Promises by using various libraries (bluebird, when, Q) and other async approaches.
I read the spec, some blog posts, and looked through some code. I learned how to
A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.
With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.
We use GraphQL to dyn
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.
We describe a model for client-server processing where the Redux model is used to minimize stateful code. This should allow live-reloading server code, and make it possible to share code (e.g. optimistic updating) between client and server.