squeedee

  global.useComponent = function(componentToRender, defaultProperties) {
    defaultProperties = _.merge({}, defaultProperties);

    beforeEach(function() {
      this.renderComponent = function(opts) {
        opts = _.assign({}, defaultProperties, opts);

        this.component = TestUtils.renderIntoDocument(
          React.createElement(componentToRender, opts)
        );

squeedee

App.changeReleaseAttribute = function(attributeName, newValue){
  AppStore.transact(function(app){
    return app.mergeIn(['release', attributeName], newValue);
  });
};

squeedee

[A1] [A2]    // reality, its a pubsub


[Sub1]      // Action namespace

[sub2]      // Store namespace - there are multiple stores

squeedee

Pivnet.ReleaseAdmin.Actions.Async = {};

Pivnet.ReleaseAdmin.Actions.Async.SubmitRelease = function(release) {
  Pivnet.ReleaseAdmin.Services.App.syncRelease(release.toJS())
  .then(Pivnet.ReleaseAdmin.Actions.Async.SubmitRelease.Completed);
};

Pivnet.ReleaseAdmin.Actions.Async.SubmitRelease.Completed = function(response) {
  var currentApp = Pivnet.ReleaseAdmin.Stores.App.get();
  var appPrime = currentApp.mergeIn(['location', 'href'], response.body.location.href);

squeedee

(update-in {:editor {:name "foo"}} [:editor] (fn [a b] (str a b)) 1)
;{:editor "{:name \"foo\"}1"}
(update-in {:editor {:name "foo"}} [:editor] (fn [a b] (str (:name a) b)) 1)
;{:editor "foo1"}
(update-in {:editor {:name "foo"}} [:editor :name] (fn [a b] (str a b)) 1)
;{:editor {:name "foo1"}}

squeedee

• Onramp.. Not smooth.
• Helper functions:
  • build parse for you (from a schema?).
  • Meaningful terms…
  • Such as fluent interfaces.. see below

Notes from my guru

Above the idea of

how easy is it to reason about

squeedee

Someone says:

Hey there's two kinds of people it would seem (maybe, wanna keep checking my facts, but this is more info than we had yesterday!)

1. [CFUser] Interested in PCF
2. [DataUser] Not interested in PCF... Data product, now that's where the money is.

It seems we should make sure they can get the things they need for who they are....

Breaking that down.

• "Can get things" -> core business proposition for pivnet. You can find the product you want.

squeedee

Business value and MMF

You should discuss the “In order to” part of the feature and pop the why stack max 5 times (ask why recursively) until you end up with one of the following business values:

• Protect revenue
• Increase revenue
• Manage cost
• Increase brand value
• Make the product remarkable
• Provide more value to your customers

squeedee

//= require ../actions/app
//= require ../stores/app
//= require ./form


var Child = React.createClass({

  getInitialState: function() {
    console.log("getInitialState");
    return {}

squeedee

(store)Release
  Version: '3.0'
  Files:
    - 'Fred'
    - 'Joe', checked: true
  EditingFiles: oldVersion 

(event)PageLoaded -> (action)rehydrate(InitalData) -> (action)releaseLoaded(ReleaseData)