samueljseay

Just recently I've been reflecting on practices and things that have or have not worked well for me as a developer at Automattic and I wanted to share a couple of things that I have perceived in my behaviours and the behaviours of others around me, that positively impacted PR reviews. These are things that if I could print them on a check list for every dev to read as they approach a PR review I would. I bet you can find many instances where I didn't live up to this too! This is aspirational for myself as well, a goal to continually strive towards.

• use github pr comments to tell people what i did and why. received universally positive feedback on this, why don't we all do it? Sometimes a code comment does not belong, but spending time helping the reviewer get context is valuable
• when reviewing any kind of UX behaviour, give me repro steps, give me a video of the behaviour. we really slow each other down async when we dont give enough detail of bugs we found or how we found them.
• Nit picking: nit pick

samueljseay

const fs = require('fs');
const path = require('path');
const { execSync } = require('child_process');

function deleteRuns(workflowName, repoNameWithOwner) {
    try {
        // Get the list of run IDs
        execSync(`gh run list --json databaseId -w ${workflowName} -L 9999 -q '.[].databaseId' > temp.txt`);

        // Read and process each run ID

samueljseay

{
  "name": "snowpack-custom-headers",
  "version": "0.0.1",
  "description": "",
  "main": "snowpack-custom-headers.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "Samuel Seay",
  "license": "MIT",

samueljseay

Use Setup Tasks to provide a first-class on-boarding experience for merchants

As a plugin author you'll often have one or more set up tasks you want to guide your user through to get the most out of your plugin. The challenge is making sure users see your tasks, and also making sure they complete them all.

The WooCommerce home screen is a consolidated landing space for users to get their store set up and effectively manage day-to-day operations for their business. Adding setup tasks to the task list alongside the usual setup steps will draw users to complete your tasks and also help them keep track of how far through the setup process they are.

We've built the user experience for you, so all that's left is just to plug your tasks in!

Getting started

samueljseay

Adding your own store management links

In the new and improved WooCommerce home screen there are 2 points of extensibility for plugin developers that have recently had some attention. The first is the setup task list, allowing you to remind the user of tasks they need to complete and keeping track of their progress for them.

The second is the store management links section. Once the user has completed the setup tasks this will display for them. This section consolidates a list of useful quick navigation links that the user can use to find features of WooCommerce.

Discoverability can be hard for users so this can be a great place to bring attention to the features of your plugin and allow users to easily find their way to the key functionality your plugin provides.

Adding your own store management links is a simple process.

samueljseay

import androidx.test.ext.junit.runners.AndroidJUnit4;
import com.facebook.litho.testing.espresso.LithoActivityTestRule;
import org.junit.Rule;
import org.junit.Test;
import org.junit.runner.RunWith;

@RunWith(AndroidJUnit4.class)
public class CardFeedActivityTest {

  @Rule

samueljseay

New Zealand MTG Code of Conduct

Welcome!

The New Zealand MTG Discord channel is a place for Magic players throughout NZ to gather, talk, trade and arrange games together. We hope you have fun!

The current admins are:

• Sam Seay

samueljseay

# install openjdk
sudo apt-get install openjdk-7-jdk

# download android sdk
wget http://dl.google.com/android/android-sdk_r24.2-linux.tgz

tar -xvf android-sdk_r24.2-linux.tgz
cd android-sdk-linux/tools

# install all sdk packages

samueljseay

// default exports
export default 42;
export default {};
export default [];
export default (1 + 2);
export default foo;
export default function () {}
export default class {}
export default function foo () {}

samueljseay

# put paths to files you don't want to lint here
path/to/files/to/ignore