Skip to content

azmisahin/azmisahin-software-web-component-trace-manager-node

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Introduction

The code architecture allows a simple method to be monitored.

Pipelines

Build Status

NPM

Example

For a quick start, let's get started.

Install

You can add the latest version to your project.

$ npm i --save trace-manager

Usage

Let's take this example of something to test.

// package define
const TraceManager = require('trace-manager')

// module instance
var tm = new TraceManager()

// any data
let data = [{ data: 'any' }]

// usage
tm.trace('trace', ...data)
tm.debug('debug', ...data)
tm.info('info', ...data)
tm.warn('warn', ...data)
tm.error('error', ...data)
tm.verbose('verbose', ...data)

Getting Started

TO DO: Things to do when getting started on this project.

Build and Test

TODO: Will apply your code and project building standards to templates.

  • The tests will be applied as in the template projects.
  • Development and operation will be planned as test/slot/production.

Contribute

TODO : The best method of making a contribution will be to comply with the following items.

  • Work with algorithms and flowcharts to solve problems.
  • Make pull requests to version control systems.
  • Stick to Architecture and Design Patterns apps.
  • Take care to develop applications with Domain Based Design / Test-oriented development approaches.
  • Stick to the architectural patterns used in abstraction software like Model-View-Controller.
  • Be consistent in executing maintainable practices with Object Oriented Programming (abstraction, encapsulation, inheritance and polymorphism...) techniques.
  • Use behavior-oriented development tools effectively.
  • Make it a habit to use Integration testing / Unit Testing / Functional Testing / Automation Tests.
  • Be persistent in applying metrics that describe how well the source code has been tested. [ have something to show at meetings: ) ]
  • Send your code with traditional commit messages, make your code understandable with static code analysis tools, "code documentation" tools.
  • Build event-driven, scalable service applications with serverless application development platforms.
  • Follow the steps to improve threading techniques like in services or mobile apps.

While starting

In the project; principles and architectural examples of development, code submission, consistent coding styles and development in team environment have been implemented.