init (e2b5546f) · Commits · lib / unicaen / observation

Module.php

0 → 100644

+42 −0

Original line number	Diff line number	Diff line
		<?php
		namespace UnicaenObservation;

		use Laminas\Mvc\ModuleRouteListener;
		use Laminas\Mvc\MvcEvent;
		use Laminas\Config\Factory as ConfigFactory;
		use Laminas\Stdlib\ArrayUtils;
		use Laminas\Stdlib\Glob;

		class Module
		{
		public function onBootstrap(MvcEvent $e)
		{
		$eventManager = $e->getApplication()->getEventManager();
		$moduleRouteListener = new ModuleRouteListener();
		$moduleRouteListener->attach($eventManager);
		}

		public function getConfig()
		{
		$configInit = [
		__DIR__ . '/config/module.config.php'
		];
		$configFiles = ArrayUtils::merge(
		$configInit,
		Glob::glob(__DIR__ . '/config/merged/{,*.}{config}.php', Glob::GLOB_BRACE)
		);

		return ConfigFactory::fromFiles($configFiles);
		}

		public function getAutoloaderConfig()
		{
		return array(
		'Laminas\Loader\StandardAutoloader' => array(
		'namespaces' => array(
		__NAMESPACE__ => __DIR__ . '/src/' . __NAMESPACE__,
		),
		),
		);
		}
		}

README.md

+41 −77

Original line number	Diff line number	Diff line
		# observation
		Bibliothèque unicaen/observation
		===


		La bibliothèque unicaen/observation est module proposant de gérer les observations déclaration des types d'observation et mise en place des instances d'observation.

		## Getting started
		La classe ObservationType
		---

		To make it easy for you to get started with GitLab, here's a list of recommended next steps.
		Un type d'observation est constitué :
		* d'un `code` unique permettant de récupérer simplement un type (idéalement regroupé dans un provider) ;
		* d'un `libelle` décrivant le type de validation elle-même ;
		* d'un `categorie` décrivant un regroupe thèmatique des observations ;

		Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
		De plus les types sont munis de l'interface/trait `HistoriqueAware`.

		## Add your files
		La classe ObservationInstance
		---

		- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
		- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
		Une instance de validation est constitée :
		* d'un `type` de validation (voir `ObservationType`) ;
		* d'un texte `observation` portant l'observation elle-même.

		```
		cd existing_repo
		git remote add origin https://git.unicaen.fr/lib/unicaen/observation.git
		git branch -M master
		git push -uf origin master
		```

		## Integrate with your tools

		- [ ] [Set up project integrations](https://git.unicaen.fr/lib/unicaen/observation/-/settings/integrations)

		## Collaborate with your team

		- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
		- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
		- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
		- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
		- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)

		## Test and Deploy

		Use the built-in continuous integration in GitLab.

		- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
		- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
		- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
		- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
		- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)

		***
		L'interface HasValidationsInterface et le trait HasValidationsTrait
		---

		# Editing this README
		Ajouter l'interface et le trait `HasObservations` va ajouter une collection `observations` (qu'il faut initialiser dans le constructeur) qui sera en charge de stocker les différentes validations.
		`HasObservations` fournit les méthodes suivantes :

		When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
		```php
		public function getObservations(): Collection;
		public function hasObservation(ObservationInstance $observationInstance): bool;
		public function hasObservationWithType(ObservationType $observationType, bool $histo = false): bool;
		public function hasObservationWithTypeCode(string $code, bool $histo = false): bool;

		## Suggestions for a good README

		Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

		## Name
		Choose a self-explaining name for your project.

		## Description
		Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

		## Badges
		On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

		## Visuals
		Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

		## Installation
		Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

		## Usage
		Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

		## Support
		Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

		## Roadmap
		If you have ideas for releases in the future, it is a good idea to list them in the README.
		public function getObservationWithTypeCode(string $code, bool $histo = false): ?ObservationInstance;
		public function addObservation(ObservationInstance $observationInstance): void;
		public function removeObservation(ObservationInstance $observationInstance): void;
		```

		## Contributing
		State if you are open to contributions and what your requirements are for accepting them.
		Remarque :
		___
		Les instances de validation seront stockées dans la table `unicaen_observation_observation_instance` et il est nécessaire de créer en linker `entite_observation`.

		For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
		Changements
		===

		You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
		6.1
		- v1

		## Authors and acknowledgment
		Show your appreciation to those who have contributed to the project.
		Scripts et description des tables
		===

		## License
		For open source projects, say how it is licensed.
		Troubleshooting
		===

		## Project status
		If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
		Aucun pour le moment ...
		No newline at end of file

composer.json

0 → 100755

+21 −0

Original line number	Diff line number	Diff line
		{
		"name": "unicaen/observation",
		"description": "Module de gestion d'observation (type et instance)",
		"repositories": [
		{
		"type": "composer",
		"url": "https://gest.unicaen.fr/packagist"
		}
		],
		"require": {
		"unicaen/app": "^6.1",
		"unicaen/privilege": "^6.1",
		"unicaen/validation": "^6.1"
		},
		"autoload": {
		"psr-0": [],
		"classmap": [
		"./Module.php"
		]
		}
		}

config/merged/observation-instance.config.php

0 → 100644

+208 −0

Original line number	Diff line number	Diff line
		<?php

		namespace UnicaenObservation;

		use Laminas\Router\Http\Literal;
		use Laminas\Router\Http\Segment;
		use UnicaenObservation\Controller\ObservationInstanceController;
		use UnicaenObservation\Controller\ObservationInstanceControllerFactory;
		use UnicaenObservation\Form\ObservationInstance\ObservationInstanceForm;
		use UnicaenObservation\Form\ObservationInstance\ObservationInstanceFormFactory;
		use UnicaenObservation\Form\ObservationInstance\ObservationInstanceHydrator;
		use UnicaenObservation\Form\ObservationInstance\ObservationInstanceHydratorFactory;
		use UnicaenObservation\Provider\Privilege\ObservationinstancePrivileges;
		use UnicaenObservation\Service\ObservationInstance\ObservationInstanceService;
		use UnicaenObservation\Service\ObservationInstance\ObservationInstanceServiceFactory;
		use UnicaenObservation\View\Helper\ObservationInstanceViewHelper;
		use UnicaenPrivilege\Guard\PrivilegeController;

		return [
		'bjyauthorize' => [
		'guards' => [
		PrivilegeController::class => [
		[
		'controller' => ObservationInstanceController::class,
		'action' => [
		'index',
		],
		'privileges' => [
		ObservationinstancePrivileges::OBSERVATIONINSTANCE_INDEX,
		],
		],
		[
		'controller' => ObservationInstanceController::class,
		'action' => [
		'afficher',
		],
		'privileges' => [
		ObservationinstancePrivileges::OBSERVATIONINSTANCE_AFFICHER,
		],
		],
		[
		'controller' => ObservationInstanceController::class,
		'action' => [
		'ajouter',
		],
		'privileges' => [
		ObservationinstancePrivileges::OBSERVATIONINSTANCE_AJOUTER,
		],
		],
		[
		'controller' => ObservationInstanceController::class,
		'action' => [
		'modifier',
		'valider',
		],
		'privileges' => [
		ObservationinstancePrivileges::OBSERVATIONINSTANCE_MODIFIER,
		],
		],
		[
		'controller' => ObservationInstanceController::class,
		'action' => [
		'historiser',
		'restaurer',
		],
		'privileges' => [
		ObservationinstancePrivileges::OBSERVATIONINSTANCE_HISTORISER,
		],
		],
		[
		'controller' => ObservationInstanceController::class,
		'action' => [
		'supprimer',
		],
		'privileges' => [
		ObservationinstancePrivileges::OBSERVATIONINSTANCE_SUPPRIMER,
		],
		],
		],
		],
		],


		'router' => [
		'routes' => [
		'observation' => [
		'type' => Literal::class,
		'options' => [
		'route' => '/observation',
		],
		'may_terminate' => false,
		'child_routes' => [
		'instance' => [
		'type' => Literal::class,
		'options' => [
		'route' => '/instance',
		'defaults' => [
		/** @see ObservationInstanceController::indexAction() */
		'controller' => ObservationInstanceController::class,
		'action' => 'index',
		],
		],
		'may_terminate' => true,
		'child_routes' => [
		'afficher' => [
		'type' => Segment::class,
		'options' => [
		'route' => '/afficher/:observation-instance',
		'defaults' => [
		/** @see ObservationInstanceController::afficherAction() */
		'action' => 'afficher',
		],
		],
		],
		'ajouter' => [
		'type' => Literal::class,
		'options' => [
		'route' => '/ajouter',
		'defaults' => [
		/** @see ObservationInstanceController::ajouterAction() */
		'action' => 'ajouter',
		],
		],
		],
		'modifier' => [
		'type' => Segment::class,
		'options' => [
		'route' => '/modifier/:observation-instance',
		'defaults' => [
		/** @see ObservationInstanceController::modifierAction() */
		'action' => 'modifier',
		],
		],
		],
		'historiser' => [
		'type' => Segment::class,
		'options' => [
		'route' => '/historiser/:observation-instance',
		'defaults' => [
		/** @see ObservationInstanceController::historiserAction() */
		'action' => 'historiser',
		],
		],
		],
		'restaurer' => [
		'type' => Segment::class,
		'options' => [
		'route' => '/restaurer/:observation-instance',
		'defaults' => [
		/** @see ObservationInstanceController::restaurerAction() */
		'action' => 'restaurer',
		],
		],
		],
		'supprimer' => [
		'type' => Segment::class,
		'options' => [
		'route' => '/supprimer/:observation-instance',
		'defaults' => [
		/** @see ObservationInstanceController::supprimerAction() */
		'action' => 'supprimer',
		],
		],
		],
		'valider' => [
		'type' => Segment::class,
		'options' => [
		'route' => '/valider/:observation-instance',
		'defaults' => [
		/** @see ObservationInstanceController::validerAction() */
		'action' => 'valider',
		],
		],
		],
		],
		],
		],
		],
		],
		],

		'service_manager' => [
		'factories' => [
		ObservationInstanceService::class => ObservationInstanceServiceFactory::class,
		],
		],
		'controllers' => [
		'factories' => [
		ObservationInstanceController::class => ObservationInstanceControllerFactory::class,
		],
		],
		'form_elements' => [
		'factories' => [
		ObservationInstanceForm::class => ObservationInstanceFormFactory::class,
		],
		],
		'hydrators' => [
		'factories' => [
		ObservationInstanceHydrator::class => ObservationInstanceHydratorFactory::class,
		],
		],
		'view_helpers' => [
		'invokables' => [
		'observationinstance' => ObservationInstanceViewHelper::class,
		],
		],

		];
		No newline at end of file

config/merged/observation-type.config.php

0 → 100644

+210 −0

File added.

Preview size limit exceeded, changes collapsed.