sohara

window.BreadPayments.setup({
  integrationKey: 'xxx-xxx-xxx',
  rtpsId: 'xxx - xxx - xxxx',
  loyaltyID: 'xxxxxx',
  buyer: {
    givenName: 'Jack',
    familyName: 'Seamus',
    additionalName: 'C.',
    birthDate: '1974-08-21',
    email: 'johncseamus@gmail.com',

sohara

SDK.setup({
  placements: [
    {
      financingType: "installments" /* card | installments */,
      locationType: "product" /* product | cart | checkout */,
      domID: "myDomElement" /* DOM element for the placement */,
    },
    {
      financingType: "installments" /* card | installments */,
      locationType: "banner" /* product | cart | banner | checkout */,

sohara

Legal Documents in Contentful

Background and requirements

SoulCycle has decided to move its published legal documents from a variety of duplicated locations in multiple codebases and DBs to a single source within Contentful, our CMS as a service.

One of the primary requirements around legal documents, specifically Terms & Conditions, is that they should be versioned to allow for major changes required by the legal department, and for riders' acceptance of these versions to be tracked over time.

Prior to migrating to Contentful this tracking of riders' acceptance was easily accomplished because the backing SQL database was a source of both the content of the legal documents and also a specific table for tracking riders' acceptance of them.

sohara

Mitigating proliferation of props in the SoulCylce UI Kit Header (aka "I want less [sic] props")

The current implemention of the UI Kit header relies entirely on various props passed to the <Header /> component to determine all aspects of what will be rendered within it and when. This allows for a more or less deterministic rendering of the component between Podium SoulCycle Site (PSS) and the older Soul Cycle Site (SCS), assuming both apps pass the same props to the <Header />.

As a component like the header is built out it's child components grow in number and complexity, resulting in a growing number of dependencies. Since the header in its current implementation is effectively a black box, the only way to provide those dependencies to the child components is to pass them down the component hierarchy as props, starting with the <Header /> invocation itself.

Here is the current invocation of the header in PSS in the _app.js file:

import { Header } from 'soulcycle-ui-kit';

sohara

import Ember from 'ember';

export default Ember.Component.extend({
  tagName: 'li',
});

sohara

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle',
  init () {
    this._super(...arguments);
    this.set('parent', this.get('store').createRecord('parent'));
   },
  
  actions: {

sohara

{
  "id": "5b30fc28c0895718b377e124",
  "publishHistory": {
    "page": 1,
    "totalCount": 3,
    "meta": {
      "collectionName": "articles",
      "modelName": "article",
      "publishable": true,
      "image": false,

sohara

sohara

import Ember from 'ember';

export default Ember.Component.extend({
});

sohara

// Running cold ember build on master, now changes

// Build 1

Build successful (55229ms) – Serving on http://localhost:4200/

Slowest Nodes (totalTime => 5% )              | Total (avg)
----------------------------------------------+---------------------
SassCompiler (7)                              | 22869ms (3267 ms)
Concat (6)                                    | 11174ms (1862 ms)