createuser --superuser --pwprompt stitchfix_owner
Set password to stitchfix_owner, as per config/database.yml
| data Failable t e = Success t | Failure e |
Like unit testing but dislike mocks and stubs? Want to keep your business logic separate from your side effects? In this blog post, I'll demonstrate a novel approach to testing which relies not on the [Dependency Injection][4] pattern, but an algebraic data structure and some simple functions.
I was recently working on a system for a real estate company which merged a
GIVEN
a video design D with elements:
| <html> | |
| <head> | |
| <title>Side by Side Tool</title> | |
| </head> | |
| <body> | |
| <div id="foo"> | |
| <label> | |
| <select name="outputType"> | |
| <option value="gen">Gen</option> | |
| <option value="comp">Comp</option> |
works with PDFV2 (e.g. RLP_BUSINESSCARD_CORP_001_EN) and PDFV3 (IMP_FLYER_2PG_EDE_101) designs, so far
admin can create configurations which specify an image set id, resource-key-to-strings mapping, and symbol-to-strings mapping
{
"imageSetId": "corcoran-4",
"resourceKeyValues": {
| { | |
| "resourceKeyValues": { | |
| "EDE_PROPERTY_ADDRESS": "999 Pine Ave." | |
| }, | |
| "symbolValues": { | |
| "view_1.disclaimer_1": "Guaranteed or Your Money Back", | |
| "agent_1.photo_1": "http://acme-broker.example.com/agents/agent-1.jpg" | |
| } | |
| } |