├── .github ├── contributing.md ├── issue_template.md └── pull_request_template.md ├── .gitignore ├── .jshintrc ├── .npmignore ├── .travis.yml ├── LICENSE ├── README.md ├── contributing.md ├── demo ├── demo-app.js ├── demo-controller.js └── index.html ├── gulpfile.js ├── karma.conf.js ├── package.json ├── paths.js ├── src └── dateTimeInput.js └── test ├── commonjs └── browserify.test.js ├── en ├── dateTimeInput.spec.js └── modelType.spec.js └── webpack ├── app.js ├── karma.conf.js ├── webpack.conf.js └── webpack.test.js /.github/contributing.md: -------------------------------------------------------------------------------- 1 | Submitting Issues 2 | ================= 3 | 4 | If you are submitting a bug, please create a [jsfiddle](http://jsfiddle.net/) demonstrating the issue. 5 | 6 | Contributing code 7 | ================= 8 | 9 | To contribute, fork the library and install gulp and dependencies. You need [node](http://nodejs.org/); use [nvm](https://github.com/creationix/nvm) or [nenv](https://github.com/ryuone/nenv) to install it. 10 | 11 | ```shell 12 | git clone https://github.com/dalelotts/angular-date-time-input.git 13 | cd angular-date-time-input 14 | npm install 15 | git checkout -b my-fix-branch develop # all patches against develop branch, please! 16 | npm test # this runs lint, complexity checks, and unit tests. 17 | ``` 18 | 19 | Very important notes 20 | ==================== 21 | 22 | * **Pull pull requests to the `master` branch will be closed.** Please submit all pull requests to the `develop` branch. 23 | * **Pull requests will not be merged without unit tests.** 24 | * **Do not include the minified files in your pull request.** 25 | * **Have good tests. If you don't have tests for every line and branch in your changes, I won't accept the PR. 26 | * **If your PR fails the CI build, I won't look at it. 27 | 28 | Gulp tasks 29 | =========== 30 | 31 | We use Gulp for managing the build. Here are some useful Gulp tasks: 32 | 33 | * `npm test` Runs all tests (webpack, commonjs, etc) checks the coding style, lints the code, calculates complexity, runs all tests, and enforces code coverage. You should make sure you do this before submitting a PR. 34 | * `gulp` The default task checks the coding style, lints the code, calculates complexity, runs the tests (not webpack or commonJS tests), and enforces code coverage. 35 | * `gulp scss` Generates the css file from the source scss. 36 | * `gulp css-lint` Lint the css files after generating. 37 | * `gulp templatecache` Generates src/js/datetimepicker.templates.js. You must re-add the IIFE around the generated code after it is generated (PR to fix this would be apprecaited) 38 | 39 | # Contributing to AngularJS 40 | 41 | We'd love for you to contribute to our source code and to make AngularJS even better than it is 42 | today! Here are the guidelines we'd like you to follow: 43 | 44 | - [Question or Problem?](#question) 45 | - [Issues and Bugs](#issue) 46 | - [Feature Requests](#feature) 47 | - [Submission Guidelines](#submit) 48 | - [Coding Rules](#rules) 49 | - [Commit Message Guidelines](#commit) 50 | - [Signing the CLA](#cla) 51 | - [Further Info](#info) 52 | 53 | ## Got a Question or Problem? 54 | 55 | If you have questions about how to use angular-date-time-input, please direct these to the [Gitter Chat Group][gitter]. 56 | 57 | ## Found an Issue? 58 | 59 | If you find a bug in the source code or a mistake in the documentation, you can help us by 60 | submitting an issue to our [GitHub Repository][issues]. Even better you can submit a Pull Request 61 | with a fix. 62 | 63 | **Localization Issues:** This directive uses the [Moment][momentI18N] for all localization. 64 | This means that any localization issues should be reproted to Moment. 65 | 66 | **Please see the [Submission Guidelines](#submit) below.** 67 | 68 | ## Want a Feature? 69 | 70 | You can request a new feature by submitting an issue to our [GitHub Repository][github]. If you 71 | would like to implement a new feature then consider what kind of change it is: 72 | 73 | * **Major Changes** that you wish to contribute to the project should be discussed first on [Gitter Chat][gitter] 74 | so that we can better coordinate our efforts, prevent duplication of work, and help you to craft the 75 | change so that it is successfully accepted into the project. 76 | * **Small Changes** can be crafted and submitted to the [GitHub Repository][github] as a Pull 77 | Request. 78 | 79 | 80 | ## Want a Doc Fix? 81 | 82 | If you want to help improve the docs, submit a PR. 83 | 84 | When naming the commit, it is advised to follow the commit message 85 | guidelines below, by starting the commit message with **docs** and 86 | reference the filename and follows the **[Commit Message Guidelines](#commit)** outlined below. 87 | 88 | ## Submission Guidelines 89 | 90 | ### Submitting an Issue 91 | Before you submit your issue search the archive, maybe your question was already answered. 92 | 93 | If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize 94 | the effort we can spend fixing issues and adding new features, by not reporting duplicate issues. 95 | Providing the following information will increase the chances of your issue being dealt with 96 | quickly: 97 | 98 | * **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps 99 | * **Motivation for or Use Case** - explain why this is a bug for you 100 | * **Angular Version(s)** - is it a regression? 101 | * **Browsers and Operating System** - is this a problem with all browsers or only specific ones? 102 | * **Reproduce the Error** - provide a live example (using [Plunker][plunker] or 103 | [JSFiddle][jsfiddle]) or an unambiguous set of steps. 104 | * **Related Issues** - has a similar issue been reported before? 105 | * **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be 106 | causing the problem (line of code or commit) 107 | 108 | Here is a great example of a well defined issue: https://github.com/angular/angular.js/issues/5069 109 | 110 | **If you get help, help others. Good karma rulez!** 111 | 112 | ### Submitting a Pull Request 113 | Before you submit your pull request consider the following guidelines: 114 | 115 | * Search [GitHub][pulls] for an open or closed Pull Request 116 | that relates to your submission. You don't want to duplicate effort. 117 | * Make your changes in a new git branch: 118 | 119 | ```shell 120 | git checkout -b my-fix-branch master 121 | ``` 122 | 123 | * Create your patch, **including appropriate test cases**. 124 | * Run the full test suite, `npm test`, and ensure that all tests pass. 125 | * Commit your changes using a descriptive commit message that follows our 126 | [commit message conventions](#commit). Adherence to the [commit message conventions](#commit) is required, 127 | because release notes are automatically generated from these messages. 128 | 129 | ```shell 130 | git commit -a 131 | ``` 132 | Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files. 133 | 134 | * Build your changes locally to ensure all the tests pass: 135 | 136 | ```shell 137 | npm test 138 | ``` 139 | 140 | * Push your branch to your fork on GitHub: 141 | 142 | ```shell 143 | git push origin my-fix-branch 144 | ``` 145 | 146 | In GitHub, send a pull request to `angular-date-time-input:develop`. 147 | If we suggest changes, then: 148 | 149 | * Make the required updates. 150 | * Re-run the test suite to ensure tests are still passing. 151 | * Commit your changes to your branch (e.g. `my-fix-branch`). 152 | * Push the changes to your GitHub repository (this will update your Pull Request). 153 | 154 | If the PR gets too outdated we may ask you to rebase and force push to update the PR: 155 | 156 | ```shell 157 | git rebase master -i 158 | git push origin my-fix-branch -f 159 | ``` 160 | 161 | _WARNING: Squashing or reverting commits and force-pushing thereafter may remove GitHub comments 162 | on code that were previously made by you or others in your commits. Avoid any form of rebasing 163 | unless necessary._ 164 | 165 | That's it! Thank you for your contribution! 166 | 167 | #### After your pull request is merged 168 | 169 | After your pull request is merged, you can safely delete your branch and pull the changes 170 | from the main (upstream) repository: 171 | 172 | * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows: 173 | 174 | ```shell 175 | git push origin --delete my-fix-branch 176 | ``` 177 | 178 | * Check out the master branch: 179 | 180 | ```shell 181 | git checkout master -f 182 | ``` 183 | 184 | * Delete the local branch: 185 | 186 | ```shell 187 | git branch -D my-fix-branch 188 | ``` 189 | 190 | * Update your master with the latest upstream version: 191 | 192 | ```shell 193 | git pull --ff upstream master 194 | ``` 195 | 196 | ## Coding Rules 197 | 198 | To ensure consistency throughout the source code, keep these rules in mind as you are working: 199 | 200 | * All features or bug fixes **must be tested** by one or more test. 201 | 202 | ## Git Commit Guidelines 203 | 204 | We have very precise rules over how our git commit messages can be formatted. This leads to **more 205 | readable messages** that are easy to follow when looking through the **project history**. But also, 206 | we use the git commit messages to **generate the AngularJS change log**. 207 | 208 | The commit message formatting can be added using a typical git workflow or through the use of a CLI wizard ([Commitizen](https://github.com/commitizen/cz-cli)). To use the wizard, run `npm run commit` in your terminal after staging your changes in git. 209 | 210 | ### Commit Message Format 211 | Each commit message consists of a **header**, a **body** and a **footer**. The header has a special 212 | format that includes a **type**, a **scope** and a **subject**: 213 | 214 | ``` 215 | (): 216 | 217 | 218 | 219 |