Prisma generated types can hinder changing the database layer later on?

Ahmed Nawaz Khan — Thu, 08 Jul 2021 15:29:47 +0000

I recently heard about prisma and wanted to try it. I really liked the simple interface it provides and the level of type saftey. however, I have one question. when we use prisma to query an entity, the response we get has a type that comes from @prisma/client ( prisma generated ). Though it has some advantages but this is where I think that a violation of open closed principle can occur. In the future if I want to change the database layer or the orm to typeorm then all the return types of my service methods have to be changed to reflect my entities (rather than previously prisma generated types). Think of it in context of nestjs where we have entities that are our common return types. Is there a way we can solve this problem with prisma? Or it is not a problem at all?

Idiomatic way to implement this in golang

Ahmed Nawaz Khan — Mon, 03 Feb 2020 16:22:12 +0000

I am experimenting to migrate a nodejs system (typescript) to golang. Its going well except i am having trouble in reproducing the following in idiomatic go

I have the following abstract class:

abstract class BaseSensor {
  beforeStart() {/*default implementation*/ }
  afterStart() {/*default implementation*/ }
  shutdown() {/*default implementation*/ }
  abstract process();

  work() {
    this.beforeStart()
    //...
    this.afterStart()
    //...
    this.process()
    //...
    this.shutdown()
  }
}

then i have some concrete classes/sensors which implement atleast the process() method and optionally any of the other lifecycle methods.

class SensorA extends BaseSensor {
  process() {
    //SensorA specific processing
  }
}

class SensorB extends BaseSensor {
  beforeStart() {
    //SensorB overriding beforeStart()
  }
  process() {
    //SensorB specific processing
  }
}

SensorA only implements the process() method and doesn't override anything else. SensorB implements process() and also overrides beforeStart().

What is the correct way of doing something like this in golang

DEV Community: Ahmed Nawaz Khan

Prisma generated types can hinder changing the database layer later on?

Idiomatic way to implement this in golang