rajesh-s

# Usage:
# Copy this file with the same name "note-link-janitor-gh-action-workflow.yml" to the <repo>/.github/workflows/ folder
# I keep all my *.md files in SRC and run janitor only on that folder. If you keep it in the root of repository or any other folder, feel free to update it on line 37 of this file
# The workflow gets triggered every time you push to your repository
name: note-link-janitor-gh-action-workflow

# Run this workflow every time a new commit pushed to your repository
on: push

jobs:

ryanflorence

// If the user has been on the page for over 12 hours, the next link
// click will do a full page transition to get new code
import React from "react";
import { BrowserRouter, useLocation } from "react-router-dom";

let hour = 3600000;

export default function StaleAppRouter(props) {
  let [isStale, setIsStale] = useState(false);

gkeep

background #e8e9ec
foreground #33374c

selection_background #d2d4dd
selection_foreground #33374c

cursor #33374c
cursor_text_color #e8e9ec

# white

jbrinley

<?php
declare( strict_types=1 );

$wp_dir = '/application/www/wp/';

$preload_patterns = [
	$wp_dir . "wp-includes/Text/Diff/Renderer.php",
	$wp_dir . "wp-includes/Text/Diff/Renderer/inline.php",
	$wp_dir . "wp-includes/SimplePie/**/*.php",
	$wp_dir . "wp-includes/SimplePie/*.php",

gkeep

background #161821
foreground #c6c8d1

selection_background #1e2132
selection_foreground #c6c8d1

cursor #d2d4de

# black
color0 #161821

dominiklohmann

cocopon

#1E2132,#2A3158,#C6C8D1,#161821,#2A3158,#C6C8D1,#B4BE82,#E27878

WebReflection

Handy Custom Elements' Patterns

^{Photo by Ricardo Gomez Angel on Unsplash}

This gist is a collection of common patterns I've personally used here and there with Custom Elements.

These patterns are all basic suggestions that could be improved, enriched, readapted, accordingly with your needs.

DavidKuennen

(function (context, trackingId, options) {
    const history = context.history;
    const doc = document;
    const nav = navigator || {};
    const storage = localStorage;
    const encode = encodeURIComponent;
    const pushState = history.pushState;
    const typeException = 'exception';
    const generateId = () => Math.random().toString(36);
    const getId = () => {

threepointone

https://twitter.com/snookca/status/1073299331262889984?s=21

‪“‬In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”

‪Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows. ‬

‪(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)‬

So the big deal about css-in-js (cij) is selectors.