tomredman

import crypto from "crypto";
import type { NextApiRequest, NextApiResponse } from "next";
import { buffer } from "micro";

export const config = {
  api: {
    bodyParser: false,
  },
};

tomredman

package org.buffer.android.helpers.customtabs;

import android.app.Activity;
import android.content.ComponentName;
import android.net.Uri;
import android.os.Bundle;
import android.support.customtabs.CustomTabsCallback;
import android.support.customtabs.CustomTabsClient;
import android.support.customtabs.CustomTabsIntent;
import android.support.customtabs.CustomTabsServiceConnection;

tomredman

/**
* Importing this file and applying this string to `className` on a hidden div
* will allow you to dynamically create tailwind components with any color you
* want, because Tailwind will compile and include all the colors it sees in your
* final CSS.
*
* BE WARNED this will increase the size of your compiled CSS file, which negates
* one of Tailwind's killer features: smallest CSS file based on just-what-you-use.
*/

tomredman

<?php

namespace App\Actions\Fortify;

use App\Models\User;
use Illuminate\Support\Facades\Hash;
use Illuminate\Support\Facades\Validator;
use Laravel\Fortify\Contracts\CreatesNewUsers;

class CreateNewUser implements CreatesNewUsers

tomredman

/*
|--------------------------------------------------------------------------
| Authentication
|--------------------------------------------------------------------------
*/
Route::post('/register', [UserController::class, 'register']);
Route::post('/login', [UserController::class, 'login']);
Route::post('/logout', [UserController::class, 'logout']);

tomredman

<?php

namespace App\Http\Controllers\Api;

use Illuminate\Http\Request;
use Illuminate\Routing\Controller;
use Illuminate\Support\Facades\Auth;
use Illuminate\Auth\Events\Registered;
use App\Actions\Fortify\CreateNewUser;
use Illuminate\Validation\ValidationException;

tomredman

In a large, nested project where I prefer to control the workspace, I run pod install --no-integrate on my root project. However, some pods don't include their required static libs correctly within their target's framework build phases.

For example, Pod-TestFlightSDK's required libTestFlight.a is excluded and removed every time I update my pods. Which required me to manually update the Pod target each time to include the static lib, which required me to automate it:

post_install do |installer_representation|
    installer_representation.project.targets.each do |target|
        if target.name == 'Pods-TestFlightSDK'
            libFile = installer_representation.project.new_file('TestFlightSDK/libTestFlight.a')
        end

tomredman

/**
 * You've probably heard it before, "explicit is better than implicit". Here's a simple
 * example of that principle in action.
 * 
 * In this example, our app has only two Fragments that can be visible at any given
 * moment: CreateFragment and TrendingFragment. Both examples achieve the same result
 * when everything is working as expected, however... 
 * 
 * In the explicit example, a final else{} branch would indiciate something's not
 * quite right with our code somewhere since we know there are only two possible

tomredman

import android.graphics.Bitmap;
import android.graphics.Canvas;
import android.graphics.Color;
import android.graphics.LinearGradient;
import android.graphics.Paint;
import android.graphics.Shader;
import android.support.annotation.ColorInt;

import com.squareup.picasso.Transformation;

tomredman

package org.buffer.android.helpers.customtabs;

import android.app.Activity;

/**
 * -----------------------
 * FAQCustomTab
 * -----------------------
 *
 * @author Tom Redman