Skip to content

Instantly share code, notes, and snippets.

🦋
Trying…

Satyajit Sahoo satya164

🦋
Trying…
Block or report user

Report or block satya164

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View react.sublime-completions
// Usage:
// Go to `Sublime Text > Browse Packages`
// Place the file under `User` directory
{
"scope": "source.js",
"completions":
[
// Top-level API
@satya164
satya164 / react-native-release.sh
Last active Dec 21, 2015
Release script for React Native (WIP)
View react-native-release.sh
#! /bin/bash
RELEASE="$1"
JAVA_VERSION="1.8"
RED="\033[0;31m"
GREEN="\033[0;32m"
BLUE="\033[0;34m"
ENDCOLOR="\033[0m"
View logger.js
/* @flow */
/* eslint-disable no-console */
let _types: ?Array<string>,
_filters: ?Array<string | RegExp>,
_history: ?Array<{ timestamp: number; args: Array<any>; }>;
const labels = {
info: '[info]',
warn: '[warn]',
View init.coffee
# Your init script
#
# Atom will evaluate this file each time a new window is opened. It is run
# after packages are loaded/activated and after the previous editor state
# has been restored.
#
# An example hack to log to the console when each text editor is saved.
#
# atom.workspace.observeTextEditors (editor) ->
# editor.onDidSave ->
@satya164
satya164 / sbc-api-react-es5.sublime-settings
Last active Sep 15, 2016
Sublime Text auto-completions for ReactJS (ES5)
View sbc-api-react-es5.sublime-settings
// Usage:
// Go to `Sublime Text > Browse Packages`
// Place the file under `User` directory
// Enable the `react-es5` in `sb-setting.sublime-settings` (refer <https://github.com/Pleasurazy/Sublime-Better-Completion/>)
{
"scope": "source.js",
"completions":
[
View lace.js
"use strict";
function Lace(selector) {
var nodes, el;
// Handle situation where called without "new" keyword
if (false === (this instanceof Lace)) {
return new Lace(selector);
}
@satya164
satya164 / MainActivity.java
Last active Dec 2, 2016
react-native-fbsdk in React Native 0.29.+
View MainActivity.java
public class MainActivity extends ReactActivity {
/**
* Returns the name of the main component registered from JavaScript.
* This is used to schedule rendering of the component.
*/
@Override
protected String getMainComponentName() {
return "MyApp";
}
View CollapsingHeaderScrollView.js
/* @flow */
import React, { PureComponent, PropTypes } from 'react';
import {
Animated,
View,
StyleSheet,
ScrollView,
} from 'react-native';
View findModuleDependencies.js
/* @flow */
import types from 'ast-types';
import { parse } from 'babylon';
const config = {
"sourceType": "module",
"plugins": [
"jsx",
"flow",
View js-style-library-wishlist.md

JavaScript Style Library Wishlist

  • Familiar CSS syntax: Using CSS syntax makes it easier to copy/paste code from devtools and the internet, and a huge productivity boost.
  • SCSS like & shorhand: Super nice to write things like &:hover without having to write selectors again.
  • Nesting media queries: Nice to nest media queries inside a style block instead of having to declare it like plain CSS.
  • Support for CSS animations: CSS animations are great :)
  • No coupling to HTML tag: HTML tags have semantic meaning, and coupling styles to HTML tags makes it harder to re-use the same styles, for example, sometimes some of my buttons and links have similar styles and I don't wanna repeat them.
  • Easy to override styles: Overriding styles is one of the main pain points. Many libs don't do anything special and just produce different class names for the styles I declare. Due to no class name having higher specificity, the styles depend on the declaration order which can produce inconsistent
You can’t perform that action at this time.