pierre-H

declare module 'Expo' {
    import { EventSubscription } from 'fbemitter';
    import { Component } from 'react';
    import { ViewStyle, ViewProperties, ColorPropType } from 'react-native';
 
    /**
     * Expo Accelerometer
     */
    export namespace Accelerometer {
        // TODO: good export type of x, y and z

tiann

#! /usr/bin/python
# -*- coding: utf-8 -*-

# @author weishu @2015/12/7

import subprocess
import os
import re
import json

jeffreypriebe

Creating new Field Types for KeystoneJS

We're currently working on making it easier to add new field types to KeystoneJS as plugins.

In the meantime, if you'd like to work on your own field type, hopefully this guide will point you in the right direction.

Keystone fields require the following:

• a {fieldType}.js file in ./lib/fieldTypes that controls the field and encapsulates options support, underscore functions, validation and updating
• the {fieldType}.js file needs to be included by ./lib/fieldTypes.js

JedWatson

// Simulate config options from your production environment by
// customising the .env file in your project's root folder.
require('dotenv')().load();

// Require keystone and i18n
var keystone = require('keystone'),
	i18n= require('i18n');

// Initialise Keystone with your project's configuration.
// See http://keystonejs.com/guide/config for available options

JedWatson

Creating new Field Types for KeystoneJS

We're currently working on making it easier to add new field types to KeystoneJS as plugins.

In the meantime, if you'd like to work on your own field type, hopefully this guide will point you in the right direction.

Keystone fields require the following:

• a {fieldType}.js file in ./lib/fieldTypes that controls the field and encapsulates options support, underscore functions, validation and updating
• the {fieldType}.js file needs to be included by ./lib/fieldTypes/index.js