| task :war do | |
| ant.war :destfile => 'pkg/project.war' do |war| | |
| war.fileset :dir => 'public' | |
| war.webinf :dir => '.' do |wi| | |
| wi.include :name => 'config/**/*' | |
| wi.include :name => 'lib/**/*' | |
| wi.include :name => 'app/**/*' | |
| wi.include :name => 'vendor/**/*' | |
| wi.include :name => 'config.ru' | |
| wi.include :name => 'Rakefile' |
| // TypeScript v 3.2.2 | |
| // | |
| // I feel like something along the way here should fail type-checking. | |
| // | |
| // The interface for Repository#saveFeed takes an attribute | |
| // with an optional `feed` property. The implementation requires the | |
| // `feed` property, and thus - I suppose - satisfies the requirement? | |
| type FeedInfo = { | |
| feed: { |
Objects w/ default method can be invoked like a function.
Objects that are well constrained (single responsibility)
can tend to end up with a single method, or at least a single method
that is important to most consumers. These methods tend to be named
by either verbing the class name (eg. UserCreator.create()) or with
I don't like shuffling configuration files around. Often chunks of config are related to a specific entity in a specific environment (like the "production redis service" or some such). ConfigKit resolves a series of URI-like references until a concrete value it located, making it easy to provide sensible defaults for local development while also pointing to environmentally-appropriate configuration in an operationally-appropriate repository (GCP Secret Manager or the like).
// In server.ts for example:| class MyClass { | |
| // if destructured renaming wasn't a thing, this is | |
| // what I'd naturally expect. But it's already | |
| // valid JS syntax for renaming, obviously. | |
| constructor({ coreService: CoreService }) { | |
| //... | |
| } | |
| // maybe-ish? | |
| constructor({ coreService as CoreService }) { |