lilac

Android's bad design

Force context object everywhere in the apis, without guaranteeing the context passed is usable, since every context has their own life cycles. This is a problem especially in asynchronous tasks or callbacks. When methods are called asynchronously, the contexts passed in may not be usable.

CoordinatorLayout can't be a container of fragment, otherwise after it is replaced with a fragment, the content might not be shown.

The app must be debuggable.

the command for Android 5.0+ to save /data/data/package.name/databases/file would be:

adb exec-out run-as package.name cat databases/file > file

Q: How to bash source env vars in an env file for docker?

A: In bash, execute commands below:

set -a
[ -f .env ] && . .env
set +a

玩家的回答

{
  "type": "answer",
  "payload": {
    "$question_id": "A" // 问题id -> 选项
  }
}

	//const tpl = makeTemplate('hello ${name}')
	//const name = 'world';
	//tpl({name});
	const makeTemplate = (templateString) => {
	return (templateData) => new Function(`{${Object.keys(templateData).join(',')}}`, 'return `' + templateString + '`')(templateData);
	}

	#!/usr/bin/env bash

	branch=`git rev-parse --abbrev-ref HEAD`
	git push origin -u $branch:branches/$branch $@

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console
	let f = (a, b) => { return a+b; }