Initialisation

**/*.log

**/*.md

**/*.php~

**/*.dist.php

**/*.dist

**/*.cache

**/._*

**/.dockerignore

**/.DS_Store

**/.git/

**/.gitattributes

**/.gitignore

**/.gitmodules

**/compose.*.yaml

**/compose.*.yml

**/compose.yaml

**/compose.yml

**/docker-compose.*.yaml

**/docker-compose.*.yml

**/docker-compose.yaml

**/docker-compose.yml

**/Dockerfile

**/Thumbs.db

.github/

docs/

public/bundles/

tests/

var/

vendor/

.editorconfig

.env.*.local

.env.local

.env.local.php

.env.test

# EditorConfig helps developers define and maintain consistent

# coding styles between different editors and IDEs

# editorconfig.org

root = true

[*]

# Change these settings to your own preference

indent_style = space

indent_size = 4

# We recommend you to keep these unchanged

end_of_line = lf

charset = utf-8

trim_trailing_whitespace = true

insert_final_newline = true

[*.{js,html,ts,tsx}]

indent_size = 2

[*.json]

indent_size = 2

[*.md]

trim_trailing_whitespace = false

[*.sh]

indent_style = tab

[*.xml{,.dist}]

indent_style = space

indent_size = 4

[*.{yaml,yml}]

trim_trailing_whitespace = false

[.github/workflows/*.yml]

indent_size = 2

[.gitmodules]

indent_style = tab

[.php_cs{,.dist}]

indent_style = space

indent_size = 4

[composer.json]

indent_size = 4

[{,docker-}compose{,.*}.{yaml,yml}]

indent_style = space

indent_size = 2

[{,*.*}Dockerfile]

indent_style = tab

[{,*.*}Caddyfile]

indent_style = tab

# .env.dist

# Le nom de domaine de smile-connect

SERVER_NAME=example.com

# Si vous utilisez un proxy, vous pouvez le définir ici

HTTP_PROXY=

HTTPS_PROXY=

# Environnement de l'application production ou dev

APP_ENV=production

# Symfony secret, vous pouvez générer un secret avec `echo $(openssl rand -hex 16)`

APP_SECRET=

# Liste des domaines de confiance, remplacez example.com par votre nom de domaine et celui de smile si il est différent

TRUSTED_HOSTS="^(localhost|exemple\.fr|.*\.exemple\.fr)$"

# Liste des proxies de confiance, notez l'IP de votre proxy si vous en avez un

TRUSTED_PROXIES=

# Informations de connexion à la base de donnée de l'api, vous pouvez modifier les valeurs à votre convenance

POSTGRES_DB=smile-connect

POSTGRES_PASSWORD=

POSTGRES_USER=

# Construit avec les informations ci-dessus, ne pas modifier

DATABASE_URL="postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@database:5432/${POSTGRES_DB}?serverVersion=16&charset=utf8"

# Informations de connexion à la base de donnée Oracle APOGEE

ORACLE_HOST=

ORACLE_PORT=

# DBNAME = SID = SERVICE_NAME

ORACLE_DBNAME=

ORACLE_USER=

ORACLE_PASSWORD=

# Informations de connexion à l'API via Basic Auth, à communiquer à Smile

API_USER=

API_PASSWORD=

* text=auto eol=lf

*.conf text eol=lf

*.html text eol=lf

*.ini text eol=lf

*.js text eol=lf

*.json text eol=lf

*.md text eol=lf

*.php text eol=lf

*.sh text eol=lf

*.yaml text eol=lf

*.yml text eol=lf

bin/console text eol=lf

composer.lock text eol=lf merge=ours

pnpm-lock.yaml text eol=lf merge=ours

*.ico binary

*.png binary

update-deps.sh export-ignore

# Contributing to API Platform

First, thank you for contributing, you're awesome!

To have your code integrated in the API Platform project, there are some rules to follow, but don't panic, it's easy!

## Reporting Bugs

If you happen to find a bug, we kindly request you to report it. However, before submitting it, please:

  * Check the [project documentation available online](https://api-platform.com/docs/)

Then, if it appears that it's a real bug, you may report it using Github by following these 3 points:

  * Check if the bug is not already reported!

  * A clear title to resume the issue

  * A description of the workflow needed to reproduce the bug,

> _NOTE:_ Don’t hesitate to give as much information as you can (OS, PHP version extensions...)

## Pull Requests

### Writing a Pull Request

You should base your changes on the `main` branch.

### Matching Coding Standards

The API Platform project follows [Symfony coding standards](https://symfony.com/doc/current/contributing/code/standards.html).

But don't worry, you can fix CS issues automatically using the [PHP CS Fixer](http://cs.sensiolabs.org/) tool:

```bash

php-cs-fixer.phar fix

```

And then, add fixed file to your commit before push.

Be sure to add only **your modified files**. If another files are fixed by cs tools, just revert it before commit.

### Sending a Pull Request

When you send a PR, just make sure that:

* You add valid test cases.

* Tests are green.

* You make a PR on the related documentation in the [api-platform/docs](https://github.com/api-platform/docs) repository.

* You make the PR on the same branch you based your changes on. If you see commits

  that you did not make in your PR, you're doing it wrong.

* Also don't forget to add a comment when you update a PR with a ping to [the maintainers](https://github.com/orgs/api-platform/people),

  so he/she will get a notification.

* Squash your commits into one commit. (see the next chapter)

Fill in the following header from the pull request template:

```markdown

| Q             | A

| ------------- | ---

| Bug fix?      | yes/no

| New feature?  | yes/no

| BC breaks?    | no

| Deprecations? | no

| Tests pass?   | yes

| Fixed tickets | #1234, #5678

| License       | MIT

| Doc PR        | api-platform/docs#1234

```

## Squash your Commits

If you have 3 commits. So start with:

```bash

git rebase -i HEAD~3

```

An editor will be opened with your 3 commits, all prefixed by `pick`.

Replace all `pick` prefixes by `fixup` (or `f`) **except the first commit** of the list.

Save and quit the editor.

After that, all your commits where squashed into the first one and the commit message of the first commit.

If you would like to rename your commit message type:

```bash

git commit --amend

```

Now force push to update your PR:

```bash

git push --force

```

# License and Copyright Attribution

When you open a Pull Request to the API Platform project, you agree to license your code under the [MIT license](../LICENSE)

and to transfer the copyright on the submitted code to [Kévin Dunglas](https://github.com/dunglas).

Be sure to you have the right to do that (if you are a professional, ask your company)!

If you include code from another project, please mention it in the Pull Request description and credit the original author.