pbnj

#!/usr/bin/env sh
# Wrapper to fetch CSRF token and authenticate via the login page

url='http://localhost:3002'
login="${url}/sign_in"

curl -sS -c cookies.txt "$login" |
    htmlstar sel -t -v "//_:input[@name='csrf_token']/@value" -o '
' | xargs -I{} curl -sS -c cookies.txt -b cookies.txt "$login" \
        --data-urlencode 'user[email]=me@example.com' \

pbnj

if exists('g:loaded_qfsigns')
  finish
endif
let g:loaded_qfsigns=1

sign define QFErr texthl=QFErrMarker text=E
sign define QFWarn texthl=QFWarnMarker text=W
sign define QFInfo texthl=QFInfoMarker text=I

augroup qfsigns

pbnj

MAKEFLAGS += --warn-undefined-variables
SHELL := bash
.SHELLFLAGS := -eu -o pipefail -c
.DEFAULT_GOAL := help
.SUFFIXES:

# ---------------------------------------------------------
# Local Variables
# ---------------------------------------------------------

pbnj

note: I wrote this for our internal documentation & guidelines at Embark so not all of it is likely relevant for other companies, but sharing here as others expressed interest in seeing it

---

What to evaluate and consider before adding usage of new third-party crates.

These are not exact requirements but questions to investigate and discuss to help reason around the health, safety, maintainability, and more around crates.

This can also be read as an opinionated guide for crate authors of what our (Embark's) guidelines and recommendations are, though should not be taken too literally.