dmitry

Booking API

• http://developer.ean.com/docs
• https://www.etbxml.com/protocol/
• https://www.homeaway.com/platform/developer-api
• https://www.roomorama.com/api/v1_0
• http://www.lodgify.com/docs/api#GET-v1-properties-pid-rates-addons_start_end_rid
• http://connect.lastminute.com/

dmitry

Mail.defaults do
  delivery_method ActionMailer::Base.delivery_method, ActionMailer::Base.smtp_settings
end

mail = Mail.deliver do
  to      'dmitry.polushkin@gmail.com'
  from    'Mikel Lindsaar <test@9flats.com>'
  subject 'First multipart email sent with Mail'

  text_part do

dmitry

# ruby script/trackable_links.rb script/a.txt "?a=2&c=3"

require 'addressable/uri'
require 'nokogiri'

class TrackableLinks
  ALLOWED_SCHEMAS = %w(http https)

  class << self
    def add(body, options)

dmitry

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout. This is also called reflow or layout thrashing, and is common performance bottleneck.

Element

Box metrics

• elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
• elem.clientLeft, elem.clientTop, elem.clientWidth, elem.clientHeight
• elem.getClientRects(), elem.getBoundingClientRect()

dmitry

• http://en.sat24.com/en/ce/rain
• http://en.sat24.com/en/ce/visual
• http://en.sat24.com/en/forecastimages/afrika/forecastprecip
• http://en.sat24.com/en/forecastimages/afrika/forecastcloud
• http://magicseaweed.com/World-Atlantic-Surf-Chart/88/?chartType=TMP

dmitry

import { Component } from "React";

export var Enhance = ComposedComponent => class extends Component {
  constructor() {
    this.state = { data: null };
  }
  componentDidMount() {
    this.setState({ data: 'Hello' });
  }
  render() {

dmitry

React now supports the use of ES6 classes as an alternative to React.createClass().

React's concept of Mixins, however, doesn't have a corollary when using ES6 classes. This left the community without an established pattern for code that both handles cross-cutting concerns and requires access to Component Life Cycle Methods.

In this gist, @sebmarkbage proposed an alternative pattern to React mixins: decorate components with a wrapping "higher order" component that handles whatever lifecycle methods it needs to and then invokes the wrapped component in its render() method, passing through props.

While a viable solution, this has a few drawbacks:

1. There's no way for the child component to override functionality defined on the higher order component.

dmitry

http://aurelien-herve.com/blog/2014/10/14/advanced-api-option-parser-for-grape/ - see comments for more implementations http://www.nicolasgarnil.me/blog/2013/crafting-ruby-grape-apis-partial-response-part1/ http://www.adamgotterer.com/post/27008214082/exposing-entities-in-grape-by-default http://googlecode.blogspot.com.ar/2010/03/making-apis-faster-introducing-partial.html

dmitry

• http://samsaffron.com/archive/2015/03/31/debugging-memory-leaks-in-ruby
• http://www.shopify.com/technology/4321572-most-memory-leaks-are-good
• http://gavinmiller.io/2015/debugging-memory-leaks-on-heroku/
• https://github.com/tmm1/rbtrace

dmitry

class ParentControllerPath
  SEGMENT = '/'

  attr_reader :path, :found

  class << self
    def routes
      Rails.application.routes
    end
  end