From f82ce4c847b927f17fbe61e7fd7bea503685f767 Mon Sep 17 00:00:00 2001 From: LboAnn Date: Thu, 12 Oct 2017 14:40:22 +0800 Subject: [PATCH] Add CDNJS version badge in README.md The badge shows the latest lib version on CDNJS and gives a link of it. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b60d131..f2afb64 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# better-dateinput-polyfill
[![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
[![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.