Version 1.0.0

Author: const-cloudinary

.code-generation/config.js

@@ -0,0 +1,71 @@
+module.exports = {
+    "SDKSpecVersion": {},
+    "langConfig": {
+        newInstanceSyntax: '(new #name(#req))#optional',
+        lang: 'PHP',
+        methodDelimiter: '->',
+        groupDelimiter: '::',
+        openQualifiersChar: '',
+        closeQualifiersChar: '',
+        closeTransformationChar: '',
+        unsupportedTxParams: [],
+        unsupportedSyntaxList: [],
+        mainTransformationString: {
+            openSyntaxString: {
+                image: '(new ImageTransformation())',
+                video: '(new VideoTransformation())',
+                media: '(new Transformation())'
+            },
+            closeSyntaxString: ';'
+        },
+        openActionChar: '(',
+        closeActionChar: ')',
+        hideActionGroups: false,
+        overwritePreset: 'php',
+        arraySeparator: ', ',
+        arrayOpen: '[',
+        arrayClose: ']',
+        formats: {
+            formatMethod: 'camelCase',
+            formatClassOrEnum: 'PascalCase',
+            formatFloat: (f) => {
+                if (!f.toString().includes('.')) {
+                    return `${f}.0` // In JS world, 1.0 is 1, so we make sure 1.0 stays 1.0
+                } else {
+                    return f;
+                }
+            }
+        },
+        methodNameMap: {
+            'signature': 'sign',
+            'url_suffix': 'suffix'
+        },
+        classNameMap: {},
+        childTransformations: {
+            image: {
+                open: "(new ImageTransformation())", // TODO Seems like we should reuse the newInstanceSyntax
+                close: '',
+            },
+            video: {
+                open: "(new VideoTransformation())",// TODO Seems like we should reuse the newInstanceSyntax
+                close: '',
+            },
+            media: {
+                open: "(new Transformation())",// TODO Seems like we should reuse the newInstanceSyntax
+                close: '',
+            }
+        },
+    },
+    "overwrites": {
+        "qualifiers": {
+            color_override: (payload) => {
+                const {qualifierDTO, langConfig} = payload;
+                const colorName = qualifierDTO.qualifiers[0].name;
+                const group = qualifierDTO.qualifiers[0].group;
+
+                // TODO this should be streamlined with how we de. al with color.
+                return `->colorOverride(Color::${colorName.toUpperCase()})`
+            }
+        }
+    }
+}

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,43 @@
+---
+name: Bug report
+about: Bug report for Cloudinary PHP Transformation Builder SDK
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Bug report for Cloudinary PHP Transformation Builder SDK
+Before proceeding, please update to the latest version and test if the issue persists
+
+## Describe the bug in a sentence or two.
+…
+
+## Issue Type (Can be multiple)
+- [ ] Build - Can’t install or import the SDK
+- [ ] Performance - Performance issues
+- [ ] Behaviour - Functions aren’t working as expected (such as generate URL)
+- [ ] Documentation - Inconsistency between the docs and behaviour
+- [ ] Other (Specify)
+
+## Steps to reproduce
+… if applicable
+
+## Error screenshots or Stack Trace (if applicable)
+…
+
+## Operating System
+- [ ] Linux
+- [ ] Windows
+- [ ] macOS
+- [ ] All
+
+## Environment and Frameworks (fill in the version numbers)
+
+- PHP Cloudinary SDK version - 0.0.0
+- PHP Version - 0.0.0 
+- Framework (Laravel, Symphony, etc) - 0.0.0
+
+## Repository
+
+If possible, please provide a link to a reproducible repository that showcases the problem

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Feature request for Cloudinary PHP Transformation Builder SDK
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Feature request for Cloudinary PHP Transformation Builder SDK
+…(If your feature is for other SDKs, please request them there)
+
+
+## Explain your use case
+… (A high level explanation of why you need this feature)
+
+## Describe the problem you’re trying to solve
+… (A more technical view of what you’d like to accomplish, and how this feature will help you achieve it)
+
+## Do you have a proposed solution?
+… (yes, no? Please elaborate if needed)

.github/pull_request_template.md

@@ -0,0 +1,29 @@
+### Brief Summary of Changes
+<!-- Provide some context as to what was changed, from an implementation standpoint. -->
+
+#### What does this PR address?
+- [ ] GitHub issue (Add reference - #XX)
+- [ ] Refactoring
+- [ ] New feature
+- [ ] Bug fix
+- [ ] Adds more tests
+
+#### Are tests included?
+- [ ] Yes
+- [ ] No
+
+#### Reviewer, please note:
+<!--
+List anything here that the reviewer should pay special attention to. This might
+include, for example:
+* Dependence on other PRs
+* Reference to other Cloudinary SDKs
+* Changes that seem arbitrary without further explanations
+-->
+
+#### Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My code follows the code style of this project.
+- [ ] My change requires a change to the documentation.
+- [ ] I ran the full test suite before pushing the changes and all of the tests pass.

.gitignore

@@ -0,0 +1,13 @@
+vendor/
+composer.lock
+tests/coverage
+output/
+.idea
+composer.phar
+docs/sami.phar
+docs/cache/
+docs/build/
+tools/dev/sanity/node_modules
+tools/dev/sanity/package-lock.json
+tools/dev/sanity/results.json
+tools/dev/sanity/TransformationSanityTest.php

.travis.yml

@@ -0,0 +1,23 @@
+language: php
+php:
+  - '7.4'
+  - '7.3'
+  - '7.2'
+  - '7.1'
+  - '7.0'
+  - '5.6'
+
+before_install:
+  - export COMPOSER_MEMORY_LIMIT=-1
+install: composer install
+
+script: vendor/bin/phpunit
+
+branches:
+  except:
+    - staging-test
+
+notifications:
+  email:
+    recipients:
+      - sdk_developers@cloudinary.com

CHANGELOG.md

@@ -0,0 +1,4 @@
+1.0.0 / 2022-05-23
+===================
+
+  * The first version of the Cloudinary PHP Transformation Builder SDK

CONTRIBUTING.md

@@ -0,0 +1,132 @@
+# Contributing to Cloudinary PHP library
+
+Contributions are welcome and greatly appreciated!
+
+## Reporting a bug
+
+- Make sure that the bug was not already reported by searching in GitHub under [Issues](https://github.com/cloudinary/cloudinary_php) and the Cloudinary [Support forms](https://support.cloudinary.com).
+- If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/cloudinary/cloudinary_php/issues/new).
+  Be sure to include a **title and clear description**, as relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
+- If you require assistance in the implementation of cloudinary_php please [submit a request](https://support.cloudinary.com/hc/en-us/requests/new) on Cloudinary's site.
+
+## Requesting a feature
+
+We would love to receive your requests!
+Please be aware that the library is used in a wide variety of environments and that some features may not be applicable to all users.
+
+- Open a GitHub [issue](https://github.com/cloudinary/cloudinary_php) describing the benefits (and possible drawbacks) of the requested feature
+
+## Fixing a bug / Implementing a new feature
+
+- Follow the instructions detailed in [Code contribution](#code-contribution)
+- Open a new GitHub pull request
+- Ensure the PR description clearly describes the bug / feature. Include relevant issue number if applicable.
+- Provide test code that covers the new code
+- The code should support:
+  - PHP >= 5.6
+
+## Code contribution
+
+When contributing code, either to fix a bug or to implement a new feature, please follow these guidelines:
+
+#### Fork the Project
+
+Fork [project on Github](https://github.com/cloudinary/cloudinary_php) and check your copy.
+
+```
+git clone https://github.com/contributor/cloudinary_php.git
+cd cloudinary_php
+git remote add upstream https://github.com/cloudinary/cloudinary_php.git
+```
+
+#### Create a Topic Branch
+
+Make sure your fork is up-to-date and create a topic branch for your feature or bug fix.
+
+```
+git checkout master
+git pull upstream master
+git checkout -b my-feature-branch
+```
+#### Rebase
+
+If you've been working on a change for a while, rebase with upstream/master.
+
+```
+git fetch upstream
+git rebase upstream/master
+git push origin my-feature-branch -f
+```
+
+
+#### Write Tests
+
+Try to write a test that reproduces the problem you're trying to fix or describes a feature you would like to build.
+
+We definitely appreciate pull requests that highlight or reproduce a problem, even without a fix.
+
+#### Write Code
+
+Implement your feature or bug fix.
+Follow the following PHP coding standards, described in [PSR-0](http://www.php-fig.org/psr/psr-0/), [PSR-1](http://www.php-fig.org/psr/psr-1/), [PSR-2](http://www.php-fig.org/psr/psr-2/) and [PSR-4](http://www.php-fig.org/psr/psr-4/) documentation.
+The code should support:
+
+  - PHP >= 5.6
+
+Make sure that `phpunit` completes without errors.
+
+#### Write Documentation
+
+Document any external behavior in the [README](README.md).
+
+#### Commit Changes
+
+Make sure git knows your name and email address:
+
+```
+git config --global user.name "Your Name"
+git config --global user.email "contributor@example.com"
+```
+
+Writing good commit logs is important. A commit log should describe what changed and why.
+
+```
+git add ...
+git commit
+```
+
+
+> Please squash your commits into a single commit when appropriate. This simplifies future cherry picks and keeps the git log clean.
+
+#### Push
+
+```
+git push origin my-feature-branch
+```
+
+#### Make a Pull Request
+
+Go to https://github.com/contributor/cloudinary_php and select your feature branch. Click the 'Pull Request' button and fill out the form. Pull requests are normally reviewed within a few days.
+Ensure the PR description clearly describes the problem and solution. Include relevant issue number if applicable.
+
+#### Rebase
+
+If you've been working on a change for a while, rebase with upstream/master.
+
+```
+git fetch upstream
+git rebase upstream/master
+git push origin my-feature-branch -f
+```
+
+#### Check on Your Pull Request
+
+Go back to your pull request after a few minutes and see whether it passed muster with Travis-CI. Everything should look green, otherwise - fix issues and amend your commit as described above.
+
+#### Be Patient
+
+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!
+
+#### Thank You
+
+Please do know that we really appreciate and value your time and work. We love you, really.

DEVELOPER_GUIDELINE.md

@@ -0,0 +1,18 @@
+# Developing Cloudinary PHP
+
+## Code style
+
+### Recommended Standards
+All code should follow the following standards:
+- [PSR-1](http://www.php-fig.org/psr/psr-1/)
+- [PSR-2](http://www.php-fig.org/psr/psr-2/)
+- [PSR-3 _Recommended_](http://www.php-fig.org/psr/psr-3/)
+- [PSR-5 _Recommended_](https://github.com/php-fig/fig-standards/blob/master/proposed/phpdoc.md)
+- [PSR-12](https://www.php-fig.org/psr/psr-12/)
+
+### PHP Code Size Control
+All code should meet default configuration of [PHPMD](https://phpmd.org/rules/codesize.html)
+
+## Tests Coverage
+All code must be covered by tests using [PHPUnit](https://phpunit.de/manual/current/en/writing-tests-for-phpunit.html)
+For functional tests unique IDs should be used and after test is done all data from remote server should be removed.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2018 Cloudinary
+
+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.