vsavkin

library test_framework;
import 'package:unittest/unittest.dart';


// RSpec like framework
typedef Closure();

class Example {
  String name;
  Closure body;

vsavkin

Building Rich Domain Models in Rails

Abstract

Domain model is an effective tool for software development. It can be used to express really complex business logic, and to verify and validate the understanding of the domain among stakeholders. Building rich domain models in Rails is hard. Primarily, because of Active Record, which doesn't play well with the domain model approach.

One way to deal with this problem is to use an ORM implementing the data mapper pattern. Unfortunately, there is no production ready ORM doing that for Ruby. DataMapper 2 is going to be the first one.

Another way is to use Active Record just as a persistence mechanism and build a rich domain model on top of it. That's what I'm going to talk about here.

vsavkin

Nrwl is Hiring Angular Engineers in Toronto!

Are you a Senior Angular engineer who continually self-trains to build cutting-edge skills? Do you love the challenge of helping teams with real-world product goals? Want to play with Angular thought-leaders and enterprise development teams?

We Have:

• Distributed company with folks all over North America

vsavkin

class TodosEffects {
  constructor(private actions: Actions, private http: Http) {}

  @Effect() addTodo = this.actions.ofType('ADD_TODO').
    concatMap(todo => this.http.post(…).
    map(() => ({type: 'TODO_ADDED', payload: todo})));
}

function todosReducer(todos: Todo[] = [], action: any): Todo[] {
  if (action.type === 'TODO_ADDED') {

vsavkin

Building Rich Domain Models in Rails.

Part 1. Decoupling Persistence.

Abstract

Domain model is an effective tool for software development. It can be used to express really complex business logic, and to verify and validate the understanding of the domain among stakeholders. Building rich domain models in Rails is hard. Primarily, because of Active Record, which doesn't play well with the domain model approach.

One way to deal with this problem is to use an ORM implementing the data mapper pattern. Unfortunately, there is no production ready ORM doing that for Ruby. DataMapper 2 is going to be the first one.

Another way is to use Active Record just as a persistence mechanism and build a rich domain model on top of it. That's what I'm going to talk about in this article.

vsavkin

// Nx Devkit
export default async function (tree: Tree, options: Schema) {
  generateFiles(
    tree,
    join(__dirname, 'files'),
    join('tools/generators', options.name),
    options
  );
  await formatFiles(tree);
}

vsavkin

blog = Blog.create
post = blog.make_post text: 'great post', location_country: 'Canada', location_city: 'Toronto'
post.make_comment text: 'great comment', location_country: 'Canada', location_city: 'Toronto'

vsavkin

@Component({
  selector: 'sub-app',
  providers: [{provide: PaymentService, useClass: CustomPaymentService1}],
  templateUrl: `subapp1.html`})
class SubApp1 {}

@Component({
  selector: 'sub-app',
  providers: [{provide: PaymentService, useClass: CustomPaymentService2}],
  templateUrl: `subapp2.html`})

vsavkin

{
  "tasks": [
    {
      "id": "react-app:build",
      "overrides": {},
      "target": {
        "project": "react-app",
        "target": "build"
      },
      "command": "npm run nx -- build react-app",

vsavkin

const execSync = require('child_process').execSync;
const commands = JSON.parse(process.argv[2]);
const projects = commands[process.argv[3]];
const target = process.argv[4];
execSync(
  `npx nx run-many --target=${target} --projects=${projects.join(
    ','
  )} --parallel`,
  {
    stdio: [0, 1, 2]