Skip to content

typedly/controller

Repository files navigation

typedly/controller

npm version GitHub issues GitHub license

A TypeScript type definitions package for various controllers.

Table of contents

Installation

1. Install peer dependencies

npm install @typedly/callback @typedly/descriptor --save-peer

2. Install the package

npm install @typedly/controller --save-peer

Api

import {
  PropertyController,
  WrappedPropertyDescriptorController,
} from '@typedly/controller';

Interface

PropertyController

The interface defines the structure for a property controller that manages property descriptors and their associated metadata.

import { PropertyController } from '@typedly/controller';

WrappedPropertyDescriptorController

The interface defines the structure for a wrapped property descriptor controller that manages it and its associated metadata.

import { WrappedPropertyDescriptorController } from '@typedly/controller';

Contributing

Your contributions are valued! If you'd like to contribute, please feel free to submit a pull request. Help is always appreciated.

Support

If you find this package useful and would like to support its and general development, you can contribute through one of the following payment methods. Your support helps maintain the packages and continue adding new.

Support via:

or via Trust Wallet

Thanks for your support!

Code of Conduct

By participating in this project, you agree to follow Code of Conduct.

GIT

Commit

Versioning

Semantic Versioning 2.0.0

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

FAQ How should I deal with revisions in the 0.y.z initial development phase?

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

License

MIT © typedly (license)

Related packages