typedly/length

Version: v0.1.1

A TypeScript type definitions package for length.

Table of contents

• Installation
• Api
  • Interface
    • LengthConfiguration
    • LengthOptions
    • LengthSetting
    • LengthSettings
    • Length
• Contributing
• Support
• Code of Conduct
• Git
  • Commit
  • Versioning
• License

Installation

npm install @typedly/length --save-peer

Api

import {
  // Interface.
  Length,
  LengthConfiguration,
  LengthOptions,
  LengthSetting,
  LengthSettings,
} from '@typedly/length';

Interface

LengthConfiguration

length-configuration.interface.ts

import { LengthConfiguration } from '@typedly/length';

// Length and pattern exact value.
const lengthConfiguration1: LengthConfiguration<0, 27, 47> = {
  value: 0,
  min: 27,
  max: 47,
};

LengthOptions

length-options.interface.ts

import { LengthOptions } from '@typedly/length';

export const length: LengthOptions<
  0,  // Value
  27, // Min
  47  // Max
> = {
  min: 27,
  max: 47,
}

LengthSetting

length-setting.interface.ts

import { LengthSetting } from '@typedly/length';

const lengthSetting: LengthSetting<
  0,  // Value
  27, // Min
  47  // Max
> = {
  length: {
    value: 0,
    min: 27,
    max: 47,
  }
}

const lengthExactSetting: LengthSetting<
  27 // Value
> = {
  length: 27
}

LengthSettings

length-settings.interface.ts

import { LengthSettings } from '@typedly/length';

const lengthSettings: LengthSettings<
  0,  // Value
  27, // Min
  47  // Max
> = {
  value: 0,
  min: 27,
  max: 47,
}

Length

length.interface.ts

import { Length } from '@typedly/length';

const length: Length<
  0,  // Value
  27, // Min
  47  // Max
> = {
  value: 0,
  min: 27,
  max: 47,
}

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:

• Stripe
• Revolut
• GitHub
• DonorBox
• Patreon

or via Trust Wallet

• XLM
• USDT (BEP20)
• ETH
• BTC
• BNB

Thanks for your support!

Code of Conduct

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

GIT

Commit

• AngularJS Git Commit Message Conventions
• Karma Git Commit Msg
• Conventional Commits

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)