DivineDominion

feature 'Contact form POST without Ajax', :js => false do
  context 'without name' do
    it 'shows the index' do
      visit_landing_page
      within('#request-form') do
        fill_in 'request-email', :with => 'test@test.de'
        fill_in 'request-anliegen', :with => 'Test'
        fill_in 'request-seiten', :with => '123'
      end
      click_button 'Anfragen'

DivineDominion

import Cocoa

/// A wrapper around any type to make Result compile
class Box<T> {
    let unbox: T
    
    init(_ value: T) {
        self.unbox = value
    }
}

DivineDominion

import Foundation

public typealias UserInfo = [NSObject : AnyObject]

public protocol DomainEvent {
    class var eventName: String { get }
    
    init(userInfo: UserInfo)
    func userInfo() -> UserInfo
}

DivineDominion

import Cocoa

// MARK: Part of Your New Toolkit 

func bind<T, U>(optional: T?, f: T -> U?) -> U? {
    
    if let x = optional {
        return f(x)
    }
    else {

DivineDominion

import Foundation

// Application Service, responsible for transactions
class CreateGroupedMonitor {

    // Domain Services:
    let monitoringService: MonitorFile
    let monitorMovalService: MoveMonitor
    
    init(monitoringService: MonitorFile, groupCreationService: CreateGroup, monitorMovalService: MoveMonitor, updateSchedule: UpdateSchedule, wordCountStrategyRegistry: WordCountStrategyRegistry, monitorRepository: MonitorRepository) {

DivineDominion

Where, instead of my inefficient approach, I execute XHR JavaScript responses. Behaves just like JangoSteve said it should for 400 or 424 HTTP response status codes.

Binds the event on $(document) so that dynamically created forms will be affected, too.

DivineDominion

Because Rails' Unobstrusive JavaScript (UJS) driver rails.js and jQuery won't execute any JavaScript in XMLHttpRequest's response bodies when the status code is 400 or 424 or something similar, I had to instruct the client (jQuery) myself to render error messages on form validation.

This is my first attempt to do so: instead of a JS request, respond with JSON and do the interface changes client-side. Problem is, the JavaScript code is sent to the client only once, hence ERB view templates aren't available during execution. I couldn't just use Rails helpers this way to refactor rendering flash messages. The HTML was spread across three places then: create.html.erb to handle synchroneous requests and render both flash messages and form validation error, entries.js.coffee to render errors and lastly create.js.erb to render success messages and insert the new entry.

It worked, and it was a fun ride since I didn't

DivineDominion

class InMemoryStrategy
  def matching(criteria)
    results = []
    domain_objects.each do |object|
      results << object if criteria.satisfied_by?(object)
    end
  end
end

DivineDominion

import Foundation

public struct Subscription<State: Any> {
    
    let subscriber: AnyStoreSubscriber
    let selector: (State -> Any)
    
    init(aSubscriber: AnyStoreSubscriber) {
        

DivineDominion

# A sample Gemfile
source "https://rubygems.org"

gem 'sinatra'
gem 'sinatra-authentication'

gem 'data_mapper'
gem 'dm-sqlite-adapter'

gem 'rdiscount'