| type CamelCase<T> = T extends `-${infer A}-${infer B}` | |
| ? `${A}${Capitalize<CamelCase<B>>}` | |
| : T extends `${infer A}-${infer B}` | |
| ? `${A}${Capitalize<CamelCase<B>>}` | |
| : T |
TypeScript supports Pick to allow you to get a "subset" object type of a given type, but there is no built-in Pick for deeper nested fields.
If you have a function that takes a large object as argument, but you don't use all of its fields, you can use Pick, Pick2, Pick3, etc to narrow down the input type to be only just what you need. This will make it easier to test your function, because when mocking the input object, you don't need to pass all fields of the "large" object.
###Redux Egghead Video Notes###
####Introduction:#### Managing state in an application is critical, and is often done haphazardly. Redux provides a state container for JavaScript applications that will help your applications behave consistently.
Redux is an evolution of the ideas presented by Facebook's Flux, avoiding the complexity found in Flux by looking to how applications are built with the Elm language.
####1st principle of Redux:#### Everything that changes in your application including the data and ui options is contained in a single object called the state tree
| angular.module('jobFoundryDirectives').directive 'spy', ($location) -> | |
| restrict: "A" | |
| require: "^scrollSpy" | |
| link: (scope, elem, attrs, scrollSpy) -> | |
| attrs.spyClass ?= "current" | |
| elem.click -> | |
| scope.$apply -> | |
| $location.hash(attrs.spy) |
