Alexander Makarov
8 years ago
54 changed files with 871 additions and 424 deletions
@ -1,45 +1,68 @@
|
||||
Yii Contributor Code of Conduct |
||||
======================= |
||||
|
||||
## Our Pledge |
||||
|
||||
As contributors and maintainers of this project, and in order to keep Yii community open and welcoming, we ask to respect all community members. |
||||
|
||||
We are committed to making participation in this project a good experience for everyone. |
||||
## Our Standards |
||||
|
||||
Examples of behavior that contributes to creating a positive environment include: |
||||
|
||||
* Using welcoming and inclusive language |
||||
* Being respectful of differing viewpoints and experiences |
||||
* Gracefully accepting constructive criticism |
||||
* Focusing on what is best for the community |
||||
* Showing empathy towards other community members |
||||
|
||||
Examples of unacceptable behavior by participants include: |
||||
|
||||
* The use of sexualized language or imagery |
||||
* The use of sexualized language or imagery and unwelcome sexual attention or |
||||
advances |
||||
* Personal attacks |
||||
* Trolling or insulting/derogatory comments |
||||
* Trolling or insulting/derogatory comments, and personal or political attacks |
||||
* Public or private harassment |
||||
* Publishing other's private information, such as physical or electronic |
||||
addresses, without explicit permission |
||||
* Other unethical or unprofessional conduct |
||||
* Other conduct which could reasonably be considered inappropriate in |
||||
a professional setting |
||||
|
||||
## Our Responsibilities |
||||
|
||||
Project maintainers are responsible for clarifying the standards of acceptable |
||||
behavior and are expected to take appropriate and fair corrective action in response |
||||
to any instances of unacceptable behavior. |
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or reject comments, |
||||
commits, code, wiki edits, issues, and other contributions that are not aligned to this |
||||
Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors |
||||
that they deem inappropriate, threatening, offensive, or harmful. |
||||
|
||||
## Scope |
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or |
||||
reject comments, commits, code, wiki edits, issues, and other contributions |
||||
that are not aligned to this Code of Conduct, or to ban temporarily or |
||||
permanently any contributor for other behaviors that they deem inappropriate, |
||||
threatening, offensive, or harmful. |
||||
This Code of Conduct applies both within project spaces and in public spaces when |
||||
an individual is representing the project or its community. Examples of representing |
||||
a project or community include posting via an official social media account, |
||||
within project GitHub, official forum or acting as an appointed representative at |
||||
an online or offline event. |
||||
|
||||
By adopting this Code of Conduct, project maintainers commit themselves to |
||||
fairly and consistently applying these principles to every aspect of managing |
||||
this project. Project maintainers who do not follow or enforce the Code of |
||||
Conduct may be permanently removed from the project team. |
||||
## Enforcement |
||||
|
||||
This Code of Conduct applies both within project spaces and in public spaces |
||||
when an individual is representing the project or its community. |
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported |
||||
by contacting core team members. All complaints will be reviewed and investigated |
||||
and will result in a response that is deemed necessary and appropriate to the circumstances. |
||||
The project team is obligated to maintain confidentiality with regard to the reporter of |
||||
an incident. Further details of specific enforcement policies may be posted separately. |
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be |
||||
reported by contacting core team members. All |
||||
complaints will be reviewed and investigated and will result in a response that |
||||
is deemed necessary and appropriate to the circumstances. Maintainers are |
||||
obligated to maintain confidentiality with regard to the reporter of an |
||||
incident. |
||||
Project maintainers who do not follow or enforce the Code of Conduct in good faith |
||||
may face temporary or permanent repercussions as determined by other members of |
||||
the project's leadership. |
||||
|
||||
## Attribution |
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], |
||||
version 1.3.0, available at |
||||
[http://contributor-covenant.org/version/1/3/0/][version] |
||||
version 1.4.0, available at |
||||
[http://contributor-covenant.org/version/1/4/][version] |
||||
|
||||
[homepage]: http://contributor-covenant.org |
||||
[version]: http://contributor-covenant.org/version/1/3/0/ |
||||
[version]: http://contributor-covenant.org/version/1/4/ |
||||
|
@ -0,0 +1,43 @@
|
||||
Yii Developer Documentation |
||||
=========================== |
||||
|
||||
This directory contains documentation about Yii Framework development and release process. |
||||
|
||||
Contributor Guidelines |
||||
---------------------- |
||||
|
||||
- [How to Report an Issue](report-an-issue.md) |
||||
- [Getting started](getting-started.md) |
||||
- [Git workflow for Yii 2 contributors](git-workflow.md) - a step by step guide on how to set up your dev environment and start contributing to Yii. |
||||
- [Yii2 Core Framework Code Style](core-code-style.md) |
||||
- [Yii2 View Code Style](view-code-style.md) |
||||
|
||||
|
||||
Documentation |
||||
------------- |
||||
|
||||
- [Translation Status](translation-status.md) - which documents are ready for translation. |
||||
- [Translation teams](translation-teams.md) |
||||
- [Translation workflow](translation-workflow.md) |
||||
|
||||
|
||||
Framework Development |
||||
--------------------- |
||||
|
||||
- [Pull request quality assurance](pull-request-qa.md) |
||||
- [Automated Tasks](automation.md), like code style fixes, automatic documentation and file generation. |
||||
- [Design Decisions](design-decisions.md) - a FAQ-like list of statements about commonly debated things. |
||||
|
||||
Versioning and Release |
||||
---------------------- |
||||
|
||||
- [Project Organization](project-organization.md) |
||||
- [Yii Versioning](versions.md) |
||||
- [Releasing a new version](release.md) |
||||
|
||||
Misc |
||||
---- |
||||
|
||||
### Exception Hierarchy |
||||
|
||||
![Yii Framework Exception Hierarchy](exception_hierarchy.png) |
@ -0,0 +1,36 @@
|
||||
Project Organization |
||||
==================== |
||||
|
||||
This document describes the organization of the Yii2 development repositories. |
||||
|
||||
1. Individual Core extensions and application templates are maintained in |
||||
separate *independent* GitHub projects under the [yiisoft](https://github.com/yiisoft) Github organization. |
||||
|
||||
Extension repository names are prefixed with `yii2-`, e.g. `yii2-gii` for the `gii` extension. |
||||
The composer package name is equal to the Github repository path, e.g. `yiisoft/yii2-gii`. |
||||
|
||||
Application template repository names are prefixed with `yii2-app-`, e.g. `yii2-app-basic` for the `basic` application template. |
||||
The composer package name is equal to the Github repository path, e.g. `yiisoft/yii2-app-basic`. |
||||
|
||||
Each extension/app project will |
||||
|
||||
* maintain its tutorial doc in its "docs" folder. The API doc will be generated on-the-fly when the extension/app is being released. |
||||
* maintain its own test code in its "tests" folder. |
||||
* maintain its own message translations and all other relevant meta code. |
||||
* track issues via the corresponding GitHub project. |
||||
|
||||
Extension repositories will be released independently as needed, Application templates will be released together with the framework. |
||||
See [versioning policy](versions.md) for more details. |
||||
|
||||
2. The `yiisoft/yii2` project is the main repository for developing Yii2 framework. |
||||
This repository provides the composer package [yiisoft/yii2-dev](https://packagist.org/packages/yiisoft/yii2-dev). |
||||
It contains the core framework code, framework unit tests, the definitive guide, and a set of build tools for framework development and release. |
||||
|
||||
Core framework bugs and feature requests are tracked in the issue tracker of this Github project. |
||||
|
||||
3. The repository `yiisoft/yii2-framework` is a read-only git subsplit of the `framework` directory of the dev project repository and |
||||
provides the composer package [yiisoft/yii2](https://packagist.org/packages/yiisoft/yii2) which is the official package to be |
||||
used when installing the framework. |
||||
|
||||
4. For development the apps and extensions can be included in the dev project structure using the |
||||
[build dev/app](git-workflow.md#prepare-the-test-environment)-Command. |
@ -0,0 +1,74 @@
|
||||
Releasing a new version |
||||
======================= |
||||
|
||||
The list of steps needed to make a release of the framework has grown over time and became |
||||
hard to manage manually, so we have created a command line tool to ensure no step is forgotten. |
||||
|
||||
Release steps overview |
||||
---------------------- |
||||
|
||||
- ... |
||||
|
||||
The release command |
||||
------------------- |
||||
|
||||
These steps are automated in the [release console command](../../build/controllers/ReleaseController.php) |
||||
which is included in the framework development repository. |
||||
|
||||
The release command can be invoked using the Yii application contained in the `build` directory of |
||||
the framework: |
||||
|
||||
./build/build help release # run this in framework repo root |
||||
|
||||
> Info: You can run the command with the `--dryRun` option to see what it would do. Using this option, |
||||
> no changes will be made and no commits or tags will be created or pushed. |
||||
|
||||
### Requirements |
||||
|
||||
The release command depends on the development environment introduced in |
||||
the [Git Workflow Document](git-workflow.md#extensions), i.e. the application |
||||
templates must be located under `/apps/` and extensions must be located under `/extensions/`. |
||||
This structure is preferably created using the `dev/app` command. |
||||
|
||||
### Version overview |
||||
|
||||
To get an overview over the versions of framework and extensions, you can run |
||||
|
||||
./build/build release/info |
||||
|
||||
You may run it with `--update` to fetch tags for all repos to get the newest information. |
||||
|
||||
### Make a release |
||||
|
||||
Making a framework release includes the following commands (apps are always released together with the framework): |
||||
|
||||
./build release framework |
||||
./build release app-basic |
||||
./build release app-advanced |
||||
|
||||
Making an extension release includes only one command (e.g. for redis): |
||||
|
||||
./build release redis |
||||
|
||||
The default release command will release a new minor version from the currently checked out branch. |
||||
To release another version thatn the default, you have to specify it using the `--version` option, e.g. |
||||
`--version=2.1.0`, or `--version=2.1.0-beta`. |
||||
|
||||
|
||||
#### Release a new major version e.g. 2.1.0 |
||||
|
||||
Releasing a new major version includes a branch change as described in the |
||||
[versioning policy](versions.md). |
||||
The following describes an example of releasing version `2.1.0` which has been |
||||
developed on the `2.1` branch derived from `master`. `master` has contained the `2.0.x` versions |
||||
before. |
||||
|
||||
- create a new branch `2.0` from `master` |
||||
- ensure composer.json does not contain a branch alias on this branch anymore. |
||||
- merge necessary changes from `master` to `2.1` |
||||
- point `master` to the lastest commit on `2.1` |
||||
- adjust composer.json branch alias for master to `2.1.x-dev`. |
||||
- delete `2.1` branch |
||||
|
||||
Now check out `master` and run the release command with the `--version=2.1.0` option. |
||||
|
@ -1,106 +1,4 @@
|
||||
Documentation status |
||||
==================== |
||||
|
||||
File | Ready for translation |
||||
------------------------------------|--------------------- |
||||
README.md | Yes |
||||
intro-yii.md | Yes |
||||
intro-upgrade-from-v1.md | Yes |
||||
start-installation.md | Yes |
||||
start-workflow.md | Yes |
||||
start-hello.md | Yes |
||||
start-forms.md | Yes |
||||
start-databases.md | Yes |
||||
start-gii.md | Yes |
||||
start-looking-ahead.md | Yes |
||||
structure-overview.md | Yes |
||||
structure-entry-scripts.md | Yes |
||||
structure-applications.md | Yes |
||||
structure-application-components.md | Yes |
||||
structure-controllers.md | Yes |
||||
structure-views.md | Yes |
||||
structure-models.md | Yes |
||||
structure-modules.md | Yes |
||||
structure-filters.md | Yes |
||||
structure-widgets.md | Yes |
||||
structure-assets.md | Yes |
||||
structure-extensions.md | Yes |
||||
runtime-overview.md | Yes |
||||
runtime-bootstrapping.md | Yes |
||||
runtime-routing.md | Yes |
||||
runtime-requests.md | Yes |
||||
runtime-responses.md | Yes |
||||
runtime-sessions-cookies.md | Yes |
||||
runtime-handling-errors.md | Yes |
||||
runtime-logging.md | Yes |
||||
concept-components.md | Yes |
||||
concept-properties.md | Yes |
||||
concept-events.md | Yes |
||||
concept-behaviors.md | Yes |
||||
concept-configurations.md | Yes |
||||
concept-aliases.md | Yes |
||||
concept-autoloading.md | Yes |
||||
concept-service-locator.md | Yes |
||||
concept-di-container.md | Yes |
||||
db-dao.md | Yes |
||||
db-query-builder.md | Yes |
||||
db-active-record.md | Yes |
||||
db-migrations.md | Yes |
||||
db-sphinx.md | |
||||
db-redis.md | |
||||
db-mongodb.md | |
||||
db-elasticsearch.md | |
||||
input-forms.md | |
||||
input-validation.md | Yes |
||||
input-file-upload.md | Yes |
||||
input-multiple-models.md | Yes |
||||
input-tabular-input.md | |
||||
output-formatting.md | Yes |
||||
output-pagination.md | Yes |
||||
output-sorting.md | Yes |
||||
output-data-providers.md | Yes |
||||
output-data-widgets.md | |
||||
output-theming.md | Yes |
||||
security-authentication.md | Yes |
||||
security-authorization.md | Yes |
||||
security-passwords.md | |
||||
security-auth-clients.md | |
||||
security-best-practices.md | |
||||
caching-overview.md | Yes |
||||
caching-data.md | Yes |
||||
caching-fragment.md | Yes |
||||
caching-page.md | Yes |
||||
caching-http.md | Yes |
||||
rest-quick-start.md | Yes |
||||
rest-resources.md | Yes |
||||
rest-controllers.md | Yes |
||||
rest-routing.md | Yes |
||||
rest-response-formatting.md | Yes |
||||
rest-authentication.md | Yes |
||||
rest-rate-limiting.md | Yes |
||||
rest-versioning.md | Yes |
||||
rest-error-handling.md | Yes |
||||
tool-debugger.md | |
||||
tool-gii.md | |
||||
tool-api-doc.md | |
||||
test-overview.md | |
||||
test-unit.md | |
||||
test-functional.md | |
||||
test-acceptance.md | |
||||
test-fixtures.md | |
||||
tutorial-advanced-app.md | |
||||
tutorial-start-from-scratch.md | |
||||
tutorial-console.md | |
||||
tutorial-i18n.md | |
||||
tutorial-mailing.md | |
||||
tutorial-performance-tuning.md | Yes |
||||
tutorial-shared-hosting.md | |
||||
tutorial-template-engines.md | |
||||
tutorial-core-validators.md | Yes |
||||
tutorial-yii-integration.md | Yes |
||||
widget-bootstrap.md | |
||||
widget-jui.md | |
||||
helper-overview.md | |
||||
helper-array.md | |
||||
helper-html.md | |
||||
helper-url.md | |
||||
Everything is ready to be translated. |
||||
|
After Width: | Height: | Size: 813 KiB |
@ -0,0 +1,39 @@
|
||||
<?php |
||||
/** |
||||
* @link http://www.yiiframework.com/ |
||||
* @copyright Copyright (c) 2008 Yii Software LLC |
||||
* @license http://www.yiiframework.com/license/ |
||||
*/ |
||||
|
||||
namespace yii\di; |
||||
|
||||
use \yii\base\InvalidConfigException; |
||||
|
||||
/** |
||||
* NotInstantiableException represents an exception caused by incorrect dependency injection container |
||||
* configuration or usage. |
||||
* |
||||
* @author Sam Mousa <sam@mousa.nl> |
||||
* @since 2.0.9 |
||||
*/ |
||||
class NotInstantiableException extends InvalidConfigException |
||||
{ |
||||
/** |
||||
* @inheritdoc |
||||
*/ |
||||
public function __construct($class, $message = null, $code = 0, \Exception $previous = null) |
||||
{ |
||||
if ($message === null) { |
||||
$message = "Can not instantiate $class."; |
||||
} |
||||
parent::__construct($message, $code, $previous); |
||||
} |
||||
|
||||
/** |
||||
* @return string the user-friendly name of this exception |
||||
*/ |
||||
public function getName() |
||||
{ |
||||
return 'Not instantiable'; |
||||
} |
||||
} |
Loading…
Reference in new issue