Skip to content

Commit

Permalink
Add CDNJS version badge in README.md
Browse files Browse the repository at this point in the history
The badge shows the latest lib version on CDNJS and gives a link of it.
  • Loading branch information
extend1994 authored Oct 12, 2017
1 parent dd47dd1 commit f82ce4c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# better-dateinput-polyfill<br>[![NPM version][npm-version]][npm-url] [![NPM downloads][npm-downloads]][npm-url] [![Build Status][travis-image]][travis-url] [![Coverage Status][coveralls-image]][coveralls-url] [![Bower version][bower-image]][bower-url]
# better-dateinput-polyfill<br>[![NPM version][npm-version]][npm-url] [![NPM downloads][npm-downloads]][npm-url] [![Build Status][travis-image]][travis-url] [![Coverage Status][coveralls-image]][coveralls-url] [![Bower version][bower-image]][bower-url] [![CDNJS version](https://img.shields.io/cdnjs/v/better-dateinput-polyfill.svg)](https://cdnjs.com/libraries/better-dateinput-polyfill)
> `input[type=date]` polyfill for [better-dom](https://github.com/chemerisuk/better-dom)
Why another date picker? The problem is that most of existing solutions do not follow standards regarding to `value` property format, that should have “a valid full-date as defined in [RFC 3339]”. In other words representation of date can vary, but the string value should have `yyyy-MM-dd` format. It helps to work with such values consistently regarding on the current language.
Expand Down

0 comments on commit f82ce4c

Please sign in to comment.