GitScrum\Contracts\ProviderInterface

Size/Duplication

Total Lines	28
Duplicated Lines	0 %

Importance

Changes

0

13 Methods

Rating	Name	Duplication	Size	Complexity
	tplUser()	0	1	?
	tplRepository()	0	1	?
	tplIssue()	0	1	?
	tplOrganization()	0	1	?
	readRepositories()	0	1	?
	createOrUpdateRepository()	0	1	?
	organization()	0	1	?
	readCollaborators()	0	1	?
	createBranches()	0	1	?
	readIssues()	0	1	?
	createOrUpdateIssue()	0	1	?
	createOrUpdateIssueComment()	0	1	?
	deleteIssueComment()	0	1	?

<?php

namespace GitScrum\Contracts;

interface ProviderInterface
{
    public function tplUser($obj);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function tplRepository($repo, $slug = false);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function tplIssue($obj, $productBacklogId);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function tplOrganization($obj);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function readRepositories($page, &$repos);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function createOrUpdateRepository($owner, $obj, $oldTitle = null);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function organization($login);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function readCollaborators($owner, $repo, $providerId = null);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function createBranches($owner, $product_backlog_id, $repo, $providerId = null);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function readIssues();

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function createOrUpdateIssue($obj);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function createOrUpdateIssueComment($obj, $verb = 'POST');

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

    public function deleteIssueComment($obj);

For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

}