first commit

Author: ddniel16

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,78 @@
+## Contributing
+
+First off, thank you for considering contributing to Android Kotlin Examples. 
+
+### 1. Where do I go from here?
+
+If you've noticed a bug or have a question,
+[search the issue tracker](https://github.com/irontec/doctrine-entity-trait/issues?q=something)
+to see if someone else has already created a ticket.
+If not, go ahead and [make one](https://github.com/irontec/doctrine-entity-trait/issues/new)!
+
+### 2. Fork & create a branch
+
+If this is something you think you can fix, then
+[fork](https://help.github.com/articles/fork-a-repo)
+and create a branch with a descriptive name.
+
+A good branch name would be (where issue #7 is the ticket you're working on):
+
+```sh
+git checkout -b 7-new-fix-for-fancy-functionality
+```
+
+#### 3. Did you find a bug?
+
+* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/irontec/doctrine-entity-trait/issues).
+
+* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/irontec/doctrine-entity-trait/issues/new). 
+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.
+
+* If possible, use the relevant bug report templates to create the issue. 
+Simply copy the content of the appropriate template into a .rb file, make the necessary changes to demonstrate the issue, 
+and **paste the content into the issue description**:
+
+### 4. Implement your fix or feature
+
+At this point, you're ready to make your changes! Feel free to ask for help;
+everyone is a beginner at first :smile_cat:
+
+### 5. Make a Pull Request
+
+At this point, you should switch back to your master branch and make sure it's
+up to date with Active Admin's master branch:
+
+```sh
+git remote add upstream [email protected]:irontec/doctrine-entity-trait.git
+git checkout master
+git pull upstream master
+```
+
+Then update your feature branch from your local copy of master, and push it!
+
+```sh
+git checkout 7-new-fix-for-fancy-functionality
+git rebase master
+git push --set-upstream origin 7-new-fix-for-fancy-functionality
+```
+
+Finally, go to GitHub and
+[make a Pull Request](https://help.github.com/articles/creating-a-pull-request)
+:D
+
+### 6. Keeping your Pull Request updated
+
+If a maintainer asks you to "rebase" your PR, they're saying that a lot of code
+has changed, and that you need to update your branch so it's easier to merge.
+
+To learn more about rebasing in Git, there are a lot of
+[good](http://git-scm.com/book/en/Git-Branching-Rebasing)
+[resources](https://help.github.com/articles/interactive-rebase),
+but here's the suggested workflow:
+
+```sh
+git checkout 7-new-fix-for-fancy-functionality
+git pull --rebase upstream master
+git push --force-with-lease 7-new-fix-for-fancy-functionality
+```

DependencyInjection/JsonExceptionResponseExtension.php

@@ -0,0 +1,27 @@
+<?php
+/**
+ * This file is part of the JsonExceptionResponseBundle.
+ */
+
+namespace Irontec\JsonExceptionResponseBundle\DependencyInjection;
+
+use \Symfony\Component\Config\FileLocator;
+use \Symfony\Component\DependencyInjection\ContainerBuilder;
+use \Symfony\Component\DependencyInjection\Loader;
+use \Symfony\Component\HttpKernel\DependencyInjection\Extension;
+
+/**
+ * @author Irontec <[email protected]>
+ * @author ddniel16 <ddniel16>
+ * @link https://github.com/irontec
+ */
+class JsonExceptionResponseExtension extends Extension
+{
+
+    public function load(array $configs, ContainerBuilder $container)
+    {
+        $loader = new Loader\XmlFileLoader($container, new FileLocator(__DIR__.'/../Resources/config'));
+        $loader->load('services.xml');
+    }
+
+}

EventListener/JsonExceptionResponseListener.php

@@ -0,0 +1,110 @@
+<?php
+/**
+ * This file is part of the JsonExceptionResponseBundle.
+ */
+
+namespace Irontec\JsonExceptionResponseBundle\EventListener;
+
+use \Symfony\Component\HttpFoundation\JsonResponse;
+use \Symfony\Component\HttpFoundation\Response;
+use \Symfony\Component\HttpKernel\Event\ExceptionEvent;
+use \Symfony\Contracts\Translation\TranslatorInterface;
+
+/**
+ * @author Irontec <[email protected]>
+ * @author ddniel16 <ddniel16>
+ * @link https://github.com/irontec
+ */
+class JsonExceptionResponseListener
+{
+
+    /**
+     * @var string
+     */
+    private $environment;
+
+    /**
+     * @var TranslatorInterface
+     */
+    private $translator;
+
+    public function __construct(string $environment, TranslatorInterface $translator)
+    {
+        $this->environment = $environment;
+        $this->translator = $translator;
+    }
+
+    /**
+     * @param ExceptionEvent $event
+     */
+    public function onKernelException(ExceptionEvent $event): void
+    {
+
+        if ($event->getRequest()->getMethod() === 'OPTIONS') {
+            $event->setResponse(new JsonResponse(array(), Response::HTTP_NO_CONTENT));
+            return;
+        }
+
+        $exception = $event->getException();
+        $code = $this->getCode($exception->getCode());
+
+        $responseData = array(
+            'error' => array(
+                'code' => $code,
+                'message' => $this->getMessage($exception->getMessage(), $code)
+            )
+        );
+
+        if ($this->environment === 'dev') {
+            $traces = $exception->getTrace();
+            if (is_array($traces)) {
+                $responseData['error']['debug'] = $traces[0];
+            }
+        }
+
+        $event->setResponse(new JsonResponse($responseData, $code));
+
+    }
+
+    /**
+     * Comprueba si el STATUS CODE es valido, en caso contrario devuelve el STATUS CODE de "HTTP_INTERNAL_SERVER_ERROR"
+     * @param int $code exception code
+     * @return int code
+     */
+    private function getCode(int $code): int
+    {
+
+        if (array_key_exists($code, Response::$statusTexts) === false) {
+            $code = Response::HTTP_INTERNAL_SERVER_ERROR;
+        }
+
+        return $code;
+
+    }
+
+    /**
+     * En base al exception message genera el mensaje de erro final.
+     * Si no hay contenido en el mensaje devuelve el mensaje del STATUS CODE
+     * El string del exception message se intenta pasar por el sistema de traducción
+     * @param string $message exception message
+     * @param int $code STATUS CODE
+     * @return string mensaje de error
+     */
+    private function getMessage(?string $message, int $code): string
+    {
+
+        $message = trim($message);
+
+        if ($message === '') {
+            return Response::$statusTexts[$code];
+        }
+
+        if ($this->translator instanceof TranslatorInterface) {
+            $message = $this->translator->trans($message);
+        }
+
+        return $message;
+
+    }
+
+}

JsonExceptionResponseBundle.php

@@ -0,0 +1,24 @@
+<?php
+/**
+ * This file is part of the JsonExceptionResponseBundle.
+ */
+
+namespace Irontec\JsonExceptionResponseBundle;
+
+use \Symfony\Component\DependencyInjection\ContainerBuilder;
+use \Symfony\Component\HttpKernel\Bundle\Bundle;
+
+/**
+ * @author Irontec <[email protected]>
+ * @author ddniel16 <ddniel16>
+ * @link https://github.com/irontec
+ */
+class JsonExceptionResponseBundle extends Bundle
+{
+
+    public function build(ContainerBuilder $container)
+    {
+        parent::build($container);
+    }
+
+}