Skip to content

Commit 63d6e22

Browse files
eitanp461eitanp461
committed
Angular2 SDK
1 parent a292306 commit 63d6e22

File tree

90 files changed

+11275
-1011
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

90 files changed

+11275
-1011
lines changed

‎.gitignore

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,35 @@
1-
21
# Logs
32
logs
43
*.log
54
npm-debug.log*
6-
config.js
5+
config.ts
6+
7+
# Ignore output of typescript compilation. They WILL be included in the package since .npmignore is empty
8+
*.js
9+
*.js.map
10+
*.d.ts
11+
12+
# Ignore generated output
13+
lib/
14+
15+
# Ignore generated typings
16+
typings/
17+
18+
# Exclude root folder *.js files and
19+
!/*.js
20+
21+
# Exclude important config files
22+
!systemjs.config.js
23+
!webpack.config.js
24+
25+
# Exclude scripts folder
26+
!/scripts/*
727

828
# Coverage directory used by tools like istanbul
929
coverage
1030

11-
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
12-
.grunt
31+
# protractor test results
32+
_test-output/
1333

1434
# Dependency directory
1535
# https://docs.npmjs.com/misc/faq#should-i-check-my-node-modules-folder-into-git
@@ -23,3 +43,4 @@ build/
2343

2444
## Directory-based project format:
2545
.idea/
46+
.vscode/

‎.npmignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
!*.js
2+
!*.js.map
3+
!*.d.ts

‎.travis.yml

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
dist: trusty
2+
sudo: required
3+
language: node_js
4+
node_js:
5+
- "node"
6+
os:
7+
- linux
8+
# env:
9+
# global:
10+
# - DBUS_SESSION_BUS_ADDRESS=/dev/null
11+
# - DISPLAY=:99.0
12+
# - CHROME_BIN=chromium-browser
13+
# before_script:
14+
# - sh -e /etc/init.d/xvfb start
15+
install:
16+
- npm install
17+
script:
18+
- npm run lint
19+
- npm run test-once
20+
# - npm run e2e

‎.yarnclean

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# test directories
2+
__tests__
3+
test
4+
tests
5+
powered-test
6+
7+
# Exclude tslint since it is secial in having a test folder under the src folder
8+
!tslint/lib/test
9+
10+
# asset directories
11+
docs
12+
doc
13+
website
14+
images
15+
assets
16+
17+
# examples
18+
example
19+
examples
20+
21+
# code coverage directories
22+
coverage
23+
.nyc_output
24+
25+
# build scripts
26+
Makefile
27+
Gulpfile.js
28+
Gruntfile.js
29+
30+
# configs
31+
.tern-project
32+
.gitattributes
33+
.editorconfig
34+
.*ignore
35+
.eslintrc
36+
.jshintrc
37+
.flowconfig
38+
.documentup.json
39+
.yarn-metadata.json
40+
.*.yml
41+
*.yml
42+
43+
# misc
44+
*.gz
45+
*.md

‎CHANGELOG.md

Lines changed: 5 additions & 87 deletions
Original file line numberDiff line numberDiff line change
@@ -1,93 +1,11 @@
11

2-
1.0.0 / 2016-03-15
2+
1.0.0-rc1 / 2016-12-19
33
==================
4+
First release
45

56
New Features
67
------------
78

8-
* Support Responsive behaviour
9-
10-
Other Changes
11-
-------------
12-
13-
* Add tests for responsive behaviour
14-
* Add spec and karma to bower ignore list
15-
* Merge pull request #42 from gilhanan/gilhanan-readme-patch-1
16-
* Add bower install instructions
17-
18-
0.2.0 / 2016-01-14
19-
==================
20-
21-
jQuery independent version
22-
--------------------------
23-
24-
* Use Cloudinary new API
25-
* Create CloudinaryProvider.
26-
* Separate sample app to with and without jQuery.
27-
28-
Other changes
29-
-------------
30-
31-
* Add setter and getter to Cloudinary provider. Serve `jQuery.cloudinary` if present.
32-
* Add NPM package.json file
33-
* Add spec file. Add Karma configuration.
34-
* Update gitignore. Update dependencies.
35-
* Rename spec file. Remove coverage and add Chrome to the karma test.
36-
* Fix sample project dependency. Remove leftover file.
37-
* Add uploaded image preview to the jQuery upload page
38-
* Support PhantomJS
39-
* Change ng-file-upload input to match version 11.
40-
* Merge pull request #40 from ArdentKid/master
41-
* bower dependency fix for "cloudinary_ng"
42-
43-
0.1.4 / 2015-08-23
44-
==================
45-
46-
* Upgrade Angular to 1.4 and ng-file-upload to version 7.0.x
47-
* Merge pull request #35 from BrittanyLea/editReadMe
48-
* Edited typo under Uploading Images section.
49-
* Change sample project's bower to install local version of the package.
50-
* Fix #16 multiple drag and drop
51-
* Modified bower configuration
52-
* upgrade angular file upload to latest version. support multiple file uploads in sample
53-
* Merge branch 'NotBobTheBuilder-master' from PR #14
54-
* Friendlier DI for minification compatibility
55-
56-
0.1.3 / Never released
57-
======================
58-
59-
* support angular 1.3 as well
60-
* Merge pull request #12 from vvvvalvalval/master
61-
* Corrected typos in sample README
62-
* Merge pull request #9 from skiomusic/master
63-
* Merge pull request #1 from nealclark/master
64-
* Observe version attribute, reload image on change
65-
66-
0.1.2 / 2014-09-04
67-
==================
68-
69-
* Merge pull request #8 from carlositocasal/bower-json-update
70-
* Correct homepage url.
71-
* Update README.md
72-
* Merge pull request #7 from iwoodruff/master
73-
* Update README.md
74-
* update readme to reflect angular file upload addition
75-
* Merge branch 'fix-angular-dependency-injection' of https://github.com/dsager/cloudinary_angular
76-
* add support for angular file upload (https://github.com/danialfarid/angular-file-upload)
77-
* version bump
78-
* added missing semicolon
79-
* define $scope parameter as injected for controller in order to avoid mangling errors
80-
* Merge pull request #5 from dsager/bower-json-main-entry
81-
* added main entry to bower.json
82-
* make publicId in ng-image dynamic. issue #1
83-
84-
v0.1.1 / 2014-05-26
85-
===================
86-
87-
* fix cloudinary_js dependency. add list enabling instructions to sample. fix sample dependency
88-
* make the package not private
89-
90-
v0.1.0 / 2014-05-26
91-
===================
92-
93-
* initial commit: 0.1.0
9+
* cl-image and cl-video components
10+
* cl-transformation attribute directive
11+
* clSrc, clHref, clSrcset attribute directives

‎CONTRIBUTING.md

Lines changed: 118 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,118 @@
1+
# Contributing to Cloudinary Angular SDK
2+
3+
Contributions are welcome and greatly appreciated!
4+
5+
## Reporting a bug
6+
7+
- Ensure that the bug was not already reported by searching in GitHub under [Issues](https://github.com/cloudinary/cloudinary-angular-2/issues) and the Cloudinary [Support forms](https://support.cloudinary.com).
8+
- If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/cloudinary/cloudinary-angular-2/issues/new).
9+
Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
10+
- If you require assistance in the implementation of the Cloudinary Angular SDK please [submit a support request](https://support.cloudinary.com/hc/en-us/requests/new) in the Cloudinary web site.
11+
12+
## Requesting a feature
13+
14+
We would love to hear your requests!
15+
Please be aware that some features may not be applicable to all users.
16+
17+
- Open a GitHub [issue](https://github.com/cloudinary/cloudinary-angular-2/issues/new) describing the benefits (and possible drawbacks) of the requested feature
18+
19+
## Fixing a bug / Implementing a new feature
20+
21+
- Follow the instructions detailed in [Code contribution](#code-contribution)
22+
- Open a new GitHub pull request
23+
- Ensure the PR description clearly describes the bug / feature. Include the relevant issue number if applicable.
24+
- Provide test code that covers the new code
25+
26+
## Code contribution
27+
28+
When contributing code, either to fix a bug or to implement a new feature, please follow these guidelines:
29+
30+
#### Fork the Project
31+
32+
Fork [project on Github](https://github.com/cloudinary/cloudinary-angular-2) and check out your copy.
33+
34+
```
35+
git clone https://github.com/contributor/cloudinary_ng.git
36+
cd cloudinary_ng
37+
git remote add upstream https://github.com/cloudinary/cloudinary-angular-2.git
38+
```
39+
40+
#### Create a Topic Branch
41+
42+
Make sure your fork is up-to-date and create a topic branch for your feature or bug fix.
43+
44+
```
45+
git checkout master
46+
git pull upstream master
47+
git checkout -b my-feature-branch
48+
```
49+
#### Rebase
50+
51+
If you've been working on a change for a while, rebase with upstream/master.
52+
53+
```
54+
git fetch upstream
55+
git rebase upstream/master
56+
git push origin my-feature-branch -f
57+
```
58+
59+
60+
#### Write Tests
61+
62+
Try to write a test that reproduces the problem you're trying to fix or describes a feature that you want to build.
63+
64+
We definitely appreciate pull requests that highlight or reproduce a problem, even without a fix.
65+
66+
#### Write Code
67+
68+
Implement your feature or bug fix.
69+
Follow [Angular's style guide](https://angular.io/styleguide).
70+
71+
#### Write Documentation
72+
73+
Document any external behavior in the [README](README.md).
74+
75+
#### Commit Changes
76+
77+
Make sure git knows your name and email address:
78+
79+
```
80+
git config --global user.name "Your Name"
81+
git config --global user.email "[email protected]"
82+
```
83+
84+
Writing good commit logs is important. A commit log should describe what changed and why.
85+
86+
```
87+
git add ...
88+
git commit
89+
```
90+
91+
92+
> Please squash your commits into a single commit when appropriate. This simplifies future cherry picks and keeps the git log clean.
93+
94+
#### Push
95+
96+
```
97+
git push origin my-feature-branch
98+
```
99+
100+
#### Make a Pull Request
101+
102+
Go to https://github.com/contributor/cloudinary_ng and select your feature branch. Click the 'Pull Request' button and fill out the form.
103+
Pull requests are usually reviewed within a few days.
104+
105+
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
106+
107+
#### Check on Your Pull Request
108+
109+
Go back to your pull request after a few minutes and see whether it passed the Travis-CI build.
110+
Everything should look green, otherwise fix issues and amend your commit as described above.
111+
112+
#### Be Patient
113+
114+
It's likely that your change will not be merged and that the nitpicky maintainers will ask you to do more, or fix seemingly benign problems. Hang on there!
115+
116+
#### Thank You
117+
118+
Please do know that we really appreciate and value your time and work, and that open source rocks!

‎LICENSE

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
The MIT License (MIT)
2+
3+
Copyright (c) 2016 https://cloudinary.com
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

0 commit comments

Comments
 (0)