aedart/model

Collection of getter- / setter-interfaces with various trait implementations, for different kinds of 'common' properties.

, _(*1)

Deprecated - Model

Package has been replaced by aedart/athenaeum All aware-of components have been migrated into the Athenaeum package., _(*2)

Collection of getters and setters-interfaces with various trait implementations, for different kinds of "common" properties. Can be used for creating DTOs., _(*3)

Contents

• When to use this
• How to install
• Quick start
  • Create your interface
  • Concrete implementation
• Available properties
• Contribution
• Acknowledgement
• Versioning
• License

When to use this

• When there is a strong need to interface what properties must be available on a given object
• (When multiple objects share the same properties)

How to install

composer require aedart/model

This package uses composer. If you do not know what that is or how it works, I recommend that you read a little about, before attempting to use this package., _(*4)

Quick start

Create your interface

In the following example, we create a simple person interface, which consists of an id, name and description;, _(*5)

<?php

namespace Acme\Contracts;

use Aedart\Model\Contracts\Integers\IdAware;
use Aedart\Model\Contracts\Strings\DescriptionAware;
use Aedart\Model\Contracts\Strings\NameAware;

interface Person extends
    IdAware,
    NameAware,
    DescriptionAware
{

}

Concrete implementation

Use the default provided traits, in order to create a concrete implementation of your interface;, _(*6)

<?php

namespace Acme\Models;

use Acme\Contracts\Person as PersonInterface;
use Aedart\Model\Traits\Strings\DescriptionTrait;
use Aedart\Model\Traits\Strings\IdTrait;
use Aedart\Model\Traits\Strings\NameTrait;

class Person implements PersonInterface
{
    use IdTrait;
    use NameTrait;
    use DescriptionTrait;   
}

Available properties

As I progress with other projects, more properties will be added..., _(*7)

Contribution

Have you found a defect ( bug or design flaw ), or do you wish improvements? In the following sections, you might find some useful information on how you can help this project. In any case, I thank you for taking the time to help me improve this project's deliverables and overall quality., _(*8)

Bug Report

If you are convinced that you have found a bug, then at the very least you should create a new issue. In that given issue, you should as a minimum describe the following;, _(*9)

• Where is the defect located
• A good, short and precise description of the defect (Why is it a defect)
• How to replicate the defect
• (A possible solution for how to resolve the defect)

When time permits it, I will review your issue and take action upon it., _(*10)

Fork, code and send pull-request

A good and well written bug report can help me a lot. Nevertheless, if you can or wish to resolve the defect by yourself, here is how you can do so;, _(*11)

• Fork this project
• Create a new local development branch for the given defect-fix
• Write your code / changes
• Create executable test-cases (prove that your changes are solid!)
• Commit and push your changes to your fork-repository
• Send a pull-request with your changes
• Drink a Beer - you earned it :)

As soon as I receive the pull-request (_and have time for it_), I will review your changes and merge them into this project. If not, I will inform you why I choose not to., _(*12)

Acknowledgement

• PHPStorm , Jetbrains; for developing the best PHP-IDE, and supporting this and other OpenSource projects
• PHPUnit , Sebastian Bergmann; By the gods ... We still know some developers, managers and decision makers, that believe good software does not require testing, at all! We cannot image working on any project, without good testing tools, such as PHPUnit.
• Codeception , Michael Bodnarchuk; for making PHPUnit even better.
• Composer & Packagist , Nils Adermann, Jordi Boggiano & et al.; amongst the best things that has happened to the PHP community.
• Git , Software Freedom Conservancy; without it… We would still be stuck in the "stone age" of software development.
• Laracasts , Jeffrey Way et al.; worth every penny…
• PHP , Rasmus Lerdorf & The PHP Group; we might be developing this in old fashioned ASP… (Shivers!)

Versioning

This package follows Semantic Versioning 2.0.0, _(*13)

License

BSD-3-Clause, Read the LICENSE file included in this package, _(*14)