mmazzarolo

Charles command-line options

Charles supports a few command line options out of the box, documented here.
Unfortunately they seem to operate only as parameters for new Charles sessions, so you won't be able to run commands on a running instance of Charles.

Start a specific Charles session

A Charles session contains all of your recorded information. It is represented by the Session window; by default a new session is automatically created when you start Charles.
Sessions can be saved from File → Save Session (⌘+S).
Once saved, if you want you can start Charles from the saved session by running:

mmazzarolo

Service Workers Tips

Reloading a service worker

Reloading a page won't update/remove the previous version of its service worker. To make sure you're using the latest version of your service worker, make sure to check the "Update on reload" toggle in the "Application" ⭢ "Service Workers" section of the Chrome DevTools.

Simulate a network condition

To simulate a network condition (e.g.: offline, 3g, etc...) in a service worker on Chrome, uncheck the "Update on reload" toggle.

mmazzarolo

2020-06-19 update:

I just published a blog post with a few other options and info on decluttering Google's search results page.

Disabling "People also search for" box in Google search results

😡😡😡

mmazzarolo

// ==========================================
//   (WIP) TYPE-SAFE ISO 3166 COUNTRY CODES
// ==========================================

/**
 * Countries data.
 * This is the source that should be updated if you want to add/remove new country codes.
 */
const countriesData = [
  ["Afghanistan", "AF", "AFG"],

mmazzarolo

// 1. Define a state variable for showing/hiding the action-button 
state = {
  isActionButtonVisible: true
}

// 2. Define a variable that will keep track of the current scroll position
_listViewOffset = 0

// 3. Add an onScroll listener to your listview/scrollview
<ListView

mmazzarolo

# iOS
app_identifier "com.myapp.app" # The bundle identifier of your app
apple_id "me@gmail.com" # Your Apple email address
team_id "1234ABCD"  # Developer Portal Team ID

# Android
json_key_file "./google-play-api-secret.json" # Path to the json secret file - Follow https://github.com/fastlane/supply#setup to get one
package_name "com.myapp.app" # Your Android app package

mmazzarolo

/**
 * RuntimeGlobalsChecker
 * 
 * You can use this utility to quickly check what variables have been added (or
 * leaked) to the global window object at runtime (by JavaScript code). 
 * By running this code, the globals checker itself is attached as a singleton
 * to the window object as "__runtimeGlobalsChecker__". 
 * You can check the runtime globals programmatically at any time by invoking
 * "window.__runtimeGlobalsChecker__.getRuntimeGlobals()".
 * 

mmazzarolo

import { useRef } from "react";
import { Animated, Easing } from "react-native";

export const useAnimation = function(initialValue: number = 0) {
  const endValue = initialValue === 0 ? 1 : 0;
  const animationValueRef = useRef<Animated.Value>(new Animated.Value(initialValue));

  const setup = (config: Partial<Animated.TimingAnimationConfig> = {}) =>
    Animated.timing(animationValueRef.current, {
      toValue: endValue,

mmazzarolo

/**
 * GlobalsDebugger
 *
 * Inspect the stack when a global variable is being set on the window object.
 * Given a global variable name, it proxies the variable name in the window
 * object adding some custom code that will be invoked whenever the variable
 * is set. The custom code will log the current stack trace and halt the code
 * execution to allow inspecting the stack and context in your browser DevTools.
 * You can use the "globalsToInspect" query-parameter to set a comma-separated
 * list of names of the variables you want to inspect.

mmazzarolo

/**
 * Fill localStorage to its maximum capacity.
 *
 * First, we find the highest order bit (the bit with the highest place value)
 * that fits in localStorage by storing localStorage an increasingly big
 * string of length 2, 4, 8, 16, etc. until it won't fill localStorage anymore.
 *
 * By working in iterations, starting with very long strings, and storing data
 * in different items, we can keep a low memory profile and reduce the number of
 * writes — making this process pretty fast.