3 replies

Naming Convention for External Service Layers

with the convention of naming layers for a service with

layer

layer

as a prefix,

layer

layer

for the "live" implementation,

layerTest

layerTest

layerLocal

layerLocal

etc when it's a static method of a service, what is the convention when creating a layer for an "external" service:

class FooBarService extends Context.Tag {}

import {FooBarService} from 'whatever/foobarservice.ts'
const QuxLive = Layer.effect(FooBarService, {}) // keep the Live suffix, add `layer` somewhere in the name, another convention?

class FooBarService extends Context.Tag {}

import {FooBarService} from 'whatever/foobarservice.ts'
const QuxLive = Layer.effect(FooBarService, {}) // keep the Live suffix, add `layer` somewhere in the name, another convention?

Effect Community•5w ago•

3 replies

bebenzer

Naming Convention for External Service Layers

with the convention of naming layers for a service with

layer

layer

as a prefix,

layer

layer

for the "live" implementation,

layerTest

layerTest

layerLocal

layerLocal

etc when it's a static method of a service, what is the convention when creating a layer for an "external" service:

class FooBarService extends Context.Tag {}

import {FooBarService} from 'whatever/foobarservice.ts'
const QuxLive = Layer.effect(FooBarService, {}) // keep the Live suffix, add `layer` somewhere in the name, another convention?

class FooBarService extends Context.Tag {}

import {FooBarService} from 'whatever/foobarservice.ts'
const QuxLive = Layer.effect(FooBarService, {}) // keep the Live suffix, add `layer` somewhere in the name, another convention?

Naming Convention for External Service Layers

Similar Threads

Naming Convention for External Service Layers

Similar Threads

Similar Threads

Similar Threads