npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ng2-daterange-picker-bfork

v2.0.3

Published

[![npm version](https://badge.fury.io/js/ng2-daterange-picker-bfork.svg)](https://badge.fury.io/js/ng2-daterange-picker-bfork)

Downloads

9

Readme

Ng2DaterangePickerBfork

npm version

daterange gif

Forked with :heart: from albertnadal

:warning: If you're using angular 5 use version 1.x, 2.x uses angular 6 :warning:

Using the component

Template format

<!-- Calendar with all the features -->
<app-daterange-picker
  [startDate]="startDate"
  [endDate]="endDate"
  [dateFormat]="'YYYY/DD/MM'"
  [rangeStart]="rangeStart"
  [rangeEnd]="rangeEnd"
  [dateTest]="dateTest"
  [ranges]="ranges"
  [showApplyButton]="showApplyButton"
  (OnSelectedDaterange)="onApply($event)"
  ></app-daterange-picker>

<!-- Minimal Calendar -->
<app-daterange-picker
  [dateFormat]="'YYYY/DD/MM'"
  (OnSelectedDaterange)="onApply($event)"
  ></app-daterange-picker>

Add Styles

CSS

Add this line to your global styles:

@import "~ng2-daterange-picker-bfork/calendar_theme.css";

SCSS

Add this line to your global styles:

@import "~ng2-daterange-picker-bfork/calendar_theme";

And you can change the following variables:

/* A very ugly theme: */

// Important variables!
$datepicker-layer-1: 10; // This is what the clickable overlay will be set
$datepicker-layer-2: 20; // The datepicker

// Breakpoints
$datepicker-breakpoint-desktop: 1020px;
$datepicker-breakpoint-tablet: 1020px;


// Colors
$datepicker-black: red ;
$datepicker-white: blue;
$datepicker-disabled: green;
$datepicker-chevron: lime;
$datepicker-invalid: navy;
$datepicker-valid: brown;
$datepicker-chosen-day: pink;

Other CSS preprocessors...

Submit a pull request!

dateFormat

ng2-daterange-picker-bfork uses moment for date validation and date formatting. dateFormat should follow the moment format.

rangeEnd / rangeStart

Only allow input dates from a specified range (i.e. dates between January 1st, 2017 to January 1st, 2018).

ranges

Set of predefined ranges. Accepts an array of objects. Use the following format:

[
  {
    dateStart: startDate,
    dateEnd: endDate,
    name: 'Range Name'
  }
]

dateTest

dateTest used to test the validity of a date. Here is an example function which makes sure the start date doesn't come before the end date:

  public dateTest(startDate, endDate): Array<String> {
    const errorArray = [];
    if (endDate.valueOf() < startDate.valueOf()) {
      errorArray.push('Start date is greater than end date');
    }
    if (startDate.valueOf() < this.rangeStart || startDate.valueOf() > this.rangeEnd) {
      errorArray.push('Start date out of range');
    }
    if (endDate.valueOf() < this.rangeStart || endDate.valueOf() > this.rangeEnd) {
      errorArray.push('End date out of range');
    }
    return errorArray;
  }

OnSelectedDaterange

Output event which emits an object in this format:

{
  startDate: <Date>,
  endDate: <Date>
}

OnDaterangeChange

Output event for when user alters the date range which emits an object in this format:

{
  startDate: <Date>,
  endDate: <Date>
}

Battling Specificity

Give an id to the component and style it globally (calendar for instance):

#calendar {
  .date-input--raised {
    z-index: 1;
  }
  .daterange__overlay {
    z-index: 1;
  }
}

Developing

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

Installing a local version into another angular project

  • $ npm run build:lib (This will generate a compiled component in the dist directory)
  • Navigate to the dist directory
  • $ npm pack (packages the component into a tar ball)
  • Navigate to another angular project.
  • $ npm install ../ng2-daterange-picker-bfork/dist/ng2-daterange-picker-bfork-x.x.x.tgz (be sure to change the version number at the end)