Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/tushar-borole/ng-sweet-alert
:loudspeaker: Sweetalert directive for angular js( angular sweetalert), without writing single javascript code
https://github.com/tushar-borole/ng-sweet-alert
Last synced: about 1 month ago
JSON representation
:loudspeaker: Sweetalert directive for angular js( angular sweetalert), without writing single javascript code
- Host: GitHub
- URL: https://github.com/tushar-borole/ng-sweet-alert
- Owner: tushar-borole
- Created: 2015-05-01T11:10:39.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2018-04-18T05:56:49.000Z (over 6 years ago)
- Last Synced: 2024-05-18T21:51:46.013Z (7 months ago)
- Language: JavaScript
- Homepage: http://tushariscoolster.github.io/ng-sweet-alert
- Size: 94.7 KB
- Stars: 151
- Watchers: 5
- Forks: 42
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
[](https://www.npmjs.com/package/ng-sweet-alert)
[](https://www.npmjs.com/package/ng-sweet-alert)
[](http://bower.io/search/?q=ng-sweet-alert)
[](https://github.com/tushariscoolster/ng-sweet-alert)
[](https://github.com/tushariscoolster/ng-sweet-alert)
# ng-sweet-alert
ng-sweet-alert is an directive for sweet alert [sweetalert]. Integration of sweet alert becomes very easy with angular js. There is no need to write a single line of javascript code. Only few html attribute is enough to use sweetalert.
## Getting Started
Install via bower
```sh
bower install ng-sweet-alert
```
Install via npm
```sh
npm install ng-sweet-alert
```
Add dependency in your module
```javascript
angular.module('yourApp',[ 'ng-sweet-alert' ]);
```
## Demo
Have a look at the [DEMO](http://tushariscoolster.github.io/ng-sweet-alert) or the [plunkr](http://plnkr.co/edit/OBhogm1ZfaGKN466Dijv?p=preview)! Edit and Fork :)
## Configure
```html
```
## Documentation
|Attribute|Options object|
|-----------------|:----------------------------|
|sweet-options | `'{title: 'Are you sure?',text: 'You will not be able to recover this imaginary file!',type: 'warning',showCancelButton: true,confirmButtonColor: '#DD6B55',confirmButtonText: 'Yes, delete it!',cancelButtonText: 'No, cancel plx!'}'` |
|sweet-confirm-option| `"{title: 'Deleted!',text: 'Your imaginary file has been deleted.',type: 'success'}"` |
|sweet-cancel-option| `{title: 'Cancelled!',text: 'Your imaginary file is safe',type: 'error'}` |
|sweet-on-cancel| `checkCancel()` |
|sweet-on-confirm| `checkConfirm()` |
----------
## Use SweetAlert as service
swal() gets two arguments;
first argument is parameters Objects (with default values).
second argument is Callback function when clicking on "OK"/"Cancel", which is a promise.
register to the promise (using 'then') and handle the resolve / reject according to your business logic.
Add 'SweetAlert' to your directive / controller / ect)
Use SweetAlert.confirm(msg, options) / SweetAlert.alert(msg, options) / SweetAlert.info(msg, options) / SweetAlert.success(msg, options)
pass arguments:
msg; String - The message to be displayed in the alert / confirm box (mandatory).
options; Object (optinal):
title: String - the title of the box.
type: String - "warning" / "info" / "error" / "success" / "" (empty string will not display a graphic icon).
showCancelButton: Boolean - shows the "cancel" button (true will behave like confirm dialog, false will behave like alert dialog).
Use returned promise;
```javascript
SweetAlert.confirm("Are you sure?", {title : "Careful now!"})
.then(function(p) { do something on success },
function(p) { do something on fail }
);
SweetAlert.success("You have successfully completed our poll!", {title: "Good job!"});
```
## Documentation: SweetAlert as a service
| Parameter|Value|
|-----------------|:----------------------------|
| msg (mandatory)| `"Are you sure you want to do that.."`
| options| `"{title: 'Delete this?', type: 'warning' showCancelButton: true}"`
----------
## Contributing
Open an issue first to discuss potential changes/additions. If you have questions with the guide, feel free to leave them as issues in the repository. If you find a typo, create a pull request. The idea is to keep the content up to date and use github’s native feature to help tell the story with issues and PR’s, which are all searchable via google. Why? Because odds are if you have a question, someone else does too! You can learn more here at about how to contribute.
*By contributing to this repository you are agreeing to make your content available subject to the license of this repository.*
### Process
1. Discuss the changes in a GitHub issue.
2. Open a Pull Request, reference the issue, and explain the change and why it adds value.
3. The Pull Request will be evaluated and either merged or declined.
## License
Use this guide. Attributions are appreciated._
### Copyright
Copyright (c) 2014-2015 [Tushar Borole](http://www.tusharborole.com)
### (The MIT License)
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
'Software'), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
##Last but not least
This is made in India with love and passion ʕ´•ᴥ•`ʔ
