The FAQ maintained by Github covers most stumbling blocks, some other tips and tricks supplied here.
Add _site
to .gitignore
. The generated site should not be uploaded to Github since its gets generated by github.
The FAQ maintained by Github covers most stumbling blocks, some other tips and tricks supplied here.
Add _site
to .gitignore
. The generated site should not be uploaded to Github since its gets generated by github.
This is a collection of information on PostgreSQL and PostGIS for what I tend to use most often.
#import <Foundation/Foundation.h> | |
#import "RCTBridgeModule.h" | |
#define RCT_EXTERN_MODULE(objc_name, objc_supername) \ | |
RCT_EXTERN_REMAP_MODULE(objc_name, objc_name, objc_supername) | |
#define RCT_EXTERN_REMAP_MODULE(js_name, objc_name, objc_supername) \ | |
objc_name : objc_supername \ | |
@end \ | |
@interface objc_name (RCTExternModule) <RCTBridgeModule> \ |
// it could be part of the LoopBackSDK module | |
// evaluate usage of node http module for ajax call | |
var http = require( 'http' ); | |
// LoopBack HTTP Interface | |
// Class that has the responsibility to call | |
// the LoopBack Application, must be instantiated for each models | |
function HTTPInterface( |
defaults: | |
- | |
scope: | |
path: "" # an empty string here means all files | |
type: "my_collection" # applies defaults only to documents in this collection (e.g. "posts") | |
values: | |
layout: "default" | |
foo: "bar" # any metadata fields can go here |
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
useSubscription
and useMutableSource
1 tearing and deopt behavior.
The tree below represents a React application mounting. During mount, two components read from an external, mutable source. The first one (List
) reads version 1 of that data and the second one (Item
) reads version 2.
N/A.