create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.
axios({ | |
url: 'http://localhost:5000/static/example.pdf', | |
method: 'GET', | |
responseType: 'blob', // important | |
}).then((response) => { | |
const url = window.URL.createObjectURL(new Blob([response.data])); | |
const link = document.createElement('a'); | |
link.href = url; | |
link.setAttribute('download', 'file.pdf'); | |
document.body.appendChild(link); |
I've worked with AngularJS for many years now and still use it in production today. Even though you can't call it ideal, given its historically-formed architecture, nobody would argue that it became quite a milestone not only for evolution of JS frameworks, but for the whole web.
It's 2017 and every new product/project has to choose a framework for development. For a long time I was sure that new Angular 2/4 (just Angular below) will become the main trend for enterprise development for years to come. I wasn't even thinking of working with something else.
Today I refuse to use it in my next project myself.
Service Workers are a new technology in modern web browsers. They augment the normal web deployment model and empower applications to deliver reliability and performance on par with natively installed code.
Service Workers have many different capabilities, but the most important is their function as a network proxy. They intercept all outgoing HTTP requests made by the application and can choose how to respond to them. For example, they can query a local cache and deliver a cached response if one is available. Proxying isn't limited to requests made through programmatic APIs (such as fetch
), but includes resources referenced in HTML and even the initial request to index.html
itself. Service Worker-based caching is thus completely programmable, and doesn't rely on server-specified caching headers.
Unlike the other scripts which make up an application (such as the Angular app bundle), the Service Worker is preserved after the user closes the tab. T
defmodule Mix.Tasks.ConvertToVerifiedRoutes do | |
@shortdoc "Fix routes" | |
use Mix.Task | |
@regex ~r/(Routes\.)(.*)_(path|url)\(.*?\)/ | |
@web_module MyAppWeb | |
def run(_) do | |
Path.wildcard("lib/**/*.*ex") |
config :wps, WPSWeb.Endpoint, | |
live_reload: [ | |
notify: [ | |
live_view: [ | |
~r"lib/wps_web/core_components.ex$", | |
~r"lib/wps_web/(live|components)/.*(ex|heex)$" | |
] | |
], | |
patterns: [ | |
~r"priv/static/(?!uploads/).*(js|css|png|jpeg|jpg|gif|svg)$", |
Use list_generators
to list available generators when available, otherwise mix help
. If you have to run generator tasks, pass --yes
. Always prefer to use generators as a basis for code generation, and then modify afterwards.
Use code interfaces on domains to define the contract for calling into Ash resources. See the Code interface guide for more.
After creating or modifying Ash code, run mix ash.codegen <short_name_describing_changes>
to ensure any required additional changes are made (like migrations are generated).