Please consider using the tags [viper-architecture], [viper-go], [viper-mode], or [viper-lang] instead of catch-all [viper]. (1) [viper-architecture] VIPER is an architectural application design pattern: {View, Interactor, Presenter, Entity, Router}. (2) [viper-mode] Viper is a Vi emulation package for Emacs. (3) [viper-go] is a configuration library for Golang. (4) [viper-lang] is for formal, separation-logic-based verifiers of programming languages.
Please consider using viper-architecture, viper-go, viper-mode, or viper-lang instead of this catch-all tag.
- VIPER is an application architecture, which stands for View, Interactor, Presenter, Entity, and Router. VIPER is intended to divide app’s logical structure into distinct layers of responsibility. It attempts to observe SOLID design patterns in the best way so as to keep code easily maintainable clean, reusable and testable.
- Viper (mode) is also a Vi emulation package for Emacs.
- Viper is also a configuration library for Golang at https://github.com/spf13/viper
- Viper is an open-source verification infrastructure, designed to simplify the development of formal, separation-logic-based verifiers for different programming languages.