Commit b1081af7 authored by Dillenn Terumalai's avatar Dillenn Terumalai
Browse files

// WIP

parent 79302459
Pipeline #1812 passed with stage
in 1 minute and 10 seconds
...@@ -25,11 +25,12 @@ publish:package: ...@@ -25,11 +25,12 @@ publish:package:
- response=$(curl -s -w "\n%{http_code}" $insecure --data $version $URL) - response=$(curl -s -w "\n%{http_code}" $insecure --data $version $URL)
- code=$(echo "$response" | tail -n 1) - code=$(echo "$response" | tail -n 1)
- body=$(echo "$response" | head -n 1) - body=$(echo "$response" | head -n 1)
# Output state information
- if [ $code -eq 201 ]; then - if [ $code -eq 201 ]; then
echo "Package created - Code $code - $body"; echo "Package created - Code $code - $body";
else else
echo "Could not create package - Code $code - $body"; echo "Could not create package - Code $code - $body";
exit 1; exit 1;
fi fi
only: only:
- tags - tags
\ No newline at end of file
# Contributing
Contributions are **welcome** and will be fully **credited**.
Please read and understand the contribution guide before creating an issue or pull request.
## Etiquette
This project is open source, and as such, the maintainers give their free time to build and maintain the source code
held within. They make the code freely available in the hope that it will be of use to other developers. It would be
extremely unfair for them to suffer abuse or anger for their hard work.
Please be considerate towards maintainers when raising issues or presenting pull requests. Let's show the
world that developers are civilized and selfless people.
It's the duty of the maintainer to ensure that all submissions to the project are of sufficient
quality to benefit the project. Many developers have different skillsets, strengths, and weaknesses. Respect the maintainer's decision, and do not be upset or abusive if your submission is not used.
## Viability
When requesting or submitting new features, first consider whether it might be useful to others. Open
source projects are used by many developers, who may have entirely different needs to your own. Think about
whether or not your feature is likely to be used by other users of the project.
## Procedure
Before filing an issue:
- Attempt to replicate the problem, to ensure that it wasn't a coincidental incident.
- Check to make sure your feature suggestion isn't already present within the project.
- Check the pull requests tab to ensure that the bug doesn't have a fix in progress.
- Check the pull requests tab to ensure that the feature isn't already in progress.
Before submitting a pull request:
- Check the codebase to ensure that your feature doesn't already exist.
- Check the pull requests to ensure that another person hasn't already submitted the feature or fix.
## Requirements
If the project maintainer has any additional requirements, you will find them listed here.
- **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)** - The easiest way to apply the conventions is to install [PHP Code Sniffer](https://pear.php.net/package/PHP_CodeSniffer).
- **Add tests!** - Your patch won't be accepted if it doesn't have tests.
- **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.
- **Consider our release cycle** - We try to follow [SemVer v2.0.0](https://semver.org/). Randomly breaking public APIs is not an option.
- **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.
- **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](https://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.
**Happy coding**!
\ No newline at end of file
# Security Policy
If you discover any security related issues, please email dillenn.terumalai@sib.swiss instead of using the issue tracker.
\ No newline at end of file
### Summary
<!-- Summarize the bug encountered concisely -->
### Steps to reproduce
<!-- How one can reproduce the issue - this is very important -->
### What is the current *bug* behavior?
<!-- What actually happens -->
### What is the expected *correct* behavior?
<!-- What you should see instead -->
### Relevant screenshots and/or logs
<!-- Paste any relevant screenshots -->
/label ~Bug
/assign @dterumal
\ No newline at end of file
### Problem to solve
<!-- What problem do we solve? -->
### Further details
<!-- Include use cases, benefits, and/or goals -->
### Proposal
<!-- What do you propose to solve this problem? -->
### Links / references
<!-- Provide any screenshot or links to websites that may be relevant to your proposal -->
/label ~Feature
/assign @dterumal
\ No newline at end of file
# Changelog
All notable changes to laravel-repository-artisan will be documented in this file.
## 1.0.0 - 2021-03-02
- initial release
\ No newline at end of file
The MIT License (MIT)
Copyright (c) :vendor_name <:author_email>
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.
\ No newline at end of file
# Laravel Repository Artisan
## Installation
You can install the package via composer:
```bash
composer config repositories.gitlab.sib.swiss/309 '{"type": "composer", "url": "https://gitlab.sib.swiss/api/v4/group/309/-/packages/composer/packages.json"}'
composer require dterumal/laravel-repository-artisan:1.0.0
```
## Usage
```php
php artisan make:interface --model=Foo FooInterface
```
This will create an interface `FooInterface` in `App/Contracts` directory using the `Foo` Eloquent model.
```php
php artisan make:repository --model=Foo --interface=FooInterface FooRepository
```
This will create a repository class `FooRepository` implementing `FooInterface` and using `Foo` Eloquent model.
**Note:** When using options such as `--model` or `--interface`, please note that if class/interface doesn't exist, the terminal will prompt you with a confirmation to automatically create it.
## Testing
```bash
composer test
```
## Changelog
Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.
## Contributing
Please see [CONTRIBUTING](.gitlab/CONTRIBUTING.md) for details.
## Security Vulnerabilities
Please review [our security policy](.gitlab/SECURITY.md) on how to report security vulnerabilities.
## Credits
- [Dillenn Terumalai](https://gitlab.sib.swiss/dterumal)
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
\ No newline at end of file
...@@ -24,7 +24,6 @@ ...@@ -24,7 +24,6 @@
</testsuite> </testsuite>
</testsuites> </testsuites>
<php> <php>
<env name="DB_CONNECTION" value="testing"/>
<env name="APP_KEY" value="base64:2fl+Ktvkfl+Fuz4Qp/A75G2RTiWVA/ZoKZvp6fiiM10="/> <env name="APP_KEY" value="base64:2fl+Ktvkfl+Fuz4Qp/A75G2RTiWVA/ZoKZvp6fiiM10="/>
</php> </php>
</phpunit> </phpunit>
\ No newline at end of file
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment