| { | |
| "version": 8, | |
| "name": "PLAN IGN", | |
| "glyphs":"https://wxs.ign.fr/static/vectorTiles/fonts/{fontstack}/{range}.pbf", | |
| "sprite": "https://wxs.ign.fr/static/vectorTiles/styles/PLAN.IGN/sprite/PlanIgn", | |
| "sources": { | |
| "plan_ign": { | |
| "type": "vector", | |
| "tiles": [ | |
| "https://wxs.ign.fr/essentiels/geoportail/tms/1.0.0/PLAN.IGN/{z}/{x}/{y}.pbf" |
| class Model | |
| # Let's say Elasticsearch needs a JSON representation of the model in order | |
| # to index it. We delegate to a specialized class to generate that JSON: | |
| def as_indexed_json | |
| ModelSerializer.new(self).as_json | |
| end | |
| end |
| # Optional but convenient: use C-b v to paste the tmux buffer. | |
| bind v paste-buffer | |
| # Do not exit from copy-mode when selecting text. | |
| # @see https://github.com/tmux/tmux/issues/337 | |
| # Note: the setting might be renamed MouseDragEndX. | |
| # Depending on whether you activated tmux or vi keybindings (I'm using vi mode): | |
| #bind -temaics-copy MouseDragEnd1Pane copy-selection -x | |
| bind -tvi-copy MouseDragEnd1Pane copy-selection -x |
| require 'ostruct' | |
| # Tiny wrapper around (custom) delayed jobs. | |
| # @see https://github.com/collectiveidea/delayed_job | |
| # @see https://github.com/collectiveidea/delayed_job#custom-jobs | |
| # | |
| # Create a new job by inheriting from Base Job: | |
| # | |
| # # app/jobs/some_task_job.rb | |
| # class SomeTask < BaseJob |
Hi!
About Lodash's forEach function, and Lodash in general…
I told you that it "abstracts away from you the chore (and complexity) of looping", so that you can focus on what really matters for your application: the collection you want to iterate through, and the piece of logic you wish to be applied for each item.
You use forEach like this:
// You first define "the collection you want to iterate through":
| import Graphics.Element exposing (..) | |
| import Text | |
| type Fifo a | |
| = Empty | Node a (List a) | |
| empty : Fifo a | |
| empty = | |
| Empty |
It's easy overlooking the basics. One must be able to clearly explain how the web works, using the dedicated vocabulary.
I recommend carefully reading the following resources:
A browser mostly "speaks" HTTP. It will craft HTTP requests for you when accessing or interacting with a website. When using JavaScript, you might also create custom HTTP requests. HTTP is the underlying language of the web.
| ### | |
| FooBar jQuery Plugin v1.0 - It makes Foo as easy as coding Bar (?). | |
| Release: 19/04/2013 | |
| Author: Joe Average <joe@average.me> | |
| http://github.com/joeaverage/foobar | |
| Licensed under the WTFPL license: http://www.wtfpl.net/txt/copying/ | |
| ### | |
| (($, window, document) -> |
| key | axis | value | |
|---|---|---|---|
| min | 1 | 2 | |
| avg | 1 | 3.6 | |
| max | 1 | 5 | |
| min | 2 | 3 | |
| avg | 2 | 8.2 | |
| max | 2 | 10 | |
| min | 3 | 0 | |
| avg | 3 | 2.6 | |
| max | 3 | 8 |
| # Our goal is to be able to run spec:bricks along spec, when | |
| # using the 'rake spec' command. | |
| # In lib/tasks/custom_specs.rake, add: | |
| require 'rake/testtask' | |
| require 'rspec/core/rake_task' | |
| namespace :spec do | |
| desc "Run bricks specs" | |
| RSpec::Core::RakeTask.new('bricks') do |spec| |