Typescript parece tener una autodocumentaci贸n en el c贸digo, definitivamente agrega m谩s valor que vailla Js, sin olvidar que el c贸digo en TS va a caer a JS.
Introduccion
D贸nde estamos y hacia d贸nde vamos
Patrones creacionales
Singleton
Singleton 101
Implementaci贸n de Singleton en JS
Contrastemos: Singleton con TS
Singleton: pros y contras
Factory
Factory 101
Diagrama de implementaci贸n de Factory
Implementaci贸n de Factory en JS
Contrastemos: Factory en TS
Factory: pros y contras
Abstract Factory
Abstract Factory 101
Diagrama de implementaci贸n de Abstract Factory
Implementaci贸n de Abstract Factory en JS
Contrastemos: Abstract Factory en TS
Abstract Factory: pros y contras
Builder
Builder 101
Diagrama de implementaci贸n de Builder
Implementaci贸n de Builder en JS
Contrastemos: Builder en TS
Builder: pros y contras
Prototype
Prototype 101
Diagrama de implementaci贸n de Prototype
Implementaci贸n de Prototype en JS
Contrastemos: Prototype en TS
Prototype: pros y contras
Conclusiones
驴Qu茅 sigue sobre patrones de dise帽o?
You don't have access to this class
Keep learning! Join and start boosting your career
If you already have an account,
Resources
What is the difference between JavaScript and TypeScript implementations?
As we get deeper into software design, the comparison between JavaScript and TypeScript becomes a fascinating topic. TypeScript, being a typed extension of JavaScript, offers significant differences in the way we can structure our code. In this case, we see that while JavaScript uses classes to define base products, TypeScript opts for interfaces, allowing flexibility without concrete methods defined in a base class.
Why use interfaces in TypeScript?
The use of interfaces in TypeScript instead of classes for defining base products allows flexibility that is especially useful when no concrete methods are required. This ability to define desired behavior without being tied to a specific implementation is crucial in more complex designs. This is achieved by using the implements keyword instead of extends, thus allowing for a clearer and more effective implementation of the required behaviors.
Data implementation and abstract method
In TypeScript, the use of functions with clearly defined data types is emphasized, even when a specific function does not currently return anything. In addition, the abstract implementation of a factory class, contrasting with the use of interfaces, is built to catch errors if the required methods are not implemented in concrete factories. This difference points out the importance of deciding between inheritance and implementation according to the requirements of the project. Inheritance is ideal for sharing a common implementation, while interfaces have a flexible structure for different behaviors.
How do typed abstractions and returns benefit?
The use of Factory in TypeScript allows you to take advantage of autocomplete, making development easier. For example, when implementing createMastodon, it is clear that the return must be of type MastodonCar and not another type such as MastodonSedan or Hashback. These differences not only improve the understanding of the code, but also optimize the developer's workflow.
Benefits of union types in factories
One of the advanced capabilities of TypeScript is to use union types to define the types of factories available in the application. This allows developers to not only clearly define which product categories or families are handled, but also to ensure correct and specific usage during coding, improving maintainability and avoiding common errors.
Thoughts on JavaScript and TypeScript versions
The choice between JavaScript and TypeScript will depend on the type of problem we are looking to solve. While TypeScript offers greater clarity and support in the development phase thanks to its static typing, some JavaScript implementations can be simpler and faster for small projects or rapid prototyping.
Which option is best for your project?
Ultimately, design preferences will depend on your specific needs:
- TypeScript, ideal if you prioritize maintainability, scalability and optimized auto-completion.
- JavaScript, optimal for rapid development or when configuration is less formalized.
If TypeScript has caught your interest, I encourage you to explore more about this powerful language. Learning platforms like Platzi offer resources that will undoubtedly enhance your skills and improve your capabilities as a developer. Remember, continuous learning is the key to success in the programming world - keep going!
Contributions 5
Questions 1
Sort by:
Sin duda alguna Typescript es un plus.
No se por que en la gran mayoria de cursos me siento que no aprendo nada, y que aveces aprendo mas con un tutorial de youtube, aqui por las rutas y los colorcitos pero creo que aveces es ver hacer cosas y ya!
//Factory no aplica porque 聽hay maas de una familia de preoductos que se creara en la fabrica// 1 create base products clases/interfacesclass watterBottle {聽 toFill(){throw new Error('abstract')}}class wineBottle {聽 toFill(){throw new Error('abstract')}}// 2 (clases/interfaces) for each family of each product that are concreteclass watterGlassBottle extends watterBottle{聽 toFill(){聽 console.log('glass bottle has been fill with watter');}}class watterPlasticBottle extends watterBottle{聽 toFill(){聽 聽 console.log('plastic bottle has been fill with watter');}
聽 }class wineGlassBottle extends wineBottle{聽 toFill(){聽 console.log('glass bottle has been fill with wine');}}
聽 class winePlasticBottle extends wineBottle { toFill(){ 聽console.log('plastic bottle has been fill with wine');}}// 3 declare abstract factory that declares the creation methods for for each 聽base productclass abstractFactory{聽 createWatterBottle(){throw new Error('abstract')}聽 createWineBottle(){throw new Error('abstract')}}//4 create the actual fabsclass glassBottleFactory extends abstractFactory{聽 createWatterBottle(){return new watterGlassBottle()聽 }聽 createWineBottle(){return new wineGlassBottle()}}class plasticBottleFactory extends abstractFactory{聽 createWatterBottle(){return new watterPlasticBottle()聽 }聽 createWineBottle(){return new winePlasticBottle()}}/\*\* se mantienen los 聽beneficios de factory+ es mas extencible聽\* si la clase base hay que cambiarla, hay que cambiar todo聽\* usalo cuando la agrupacion en familias sea posible (glass /plastic聽\*/function createBottleFactory(type){聽 const factories={ plastic:plasticBottleFactory,聽 聽 glass:glassBottleFactory
聽 }聽 const Factory=factories\[type];聽 return new Factory ();
}
function appBottleFactory(Factory){const watter=Factory.createWatterBottle()const wine= Factory.createWineBottle()watter.toFill();wine.toFill();}appBottleFactory(createBottleFactory('plastic'));appBottleFactory(createBottleFactory('glass'));
Creo que ser铆a mejor que las interfaces MastodonCar y RhinoCar tuvieran m茅todos diferentes para que tenga m谩s sentido, ya que ambas interfaces tienen la misma firma del m茅todo.
Want to see more contributions, questions and answers from the community?