37f7b426b6
Implements automatic creation of required plugin pages (Community Login, Trainer Registration, Trainer Dashboard) upon plugin activation. This addresses E2E test failures caused by missing pages in the test environment. - Adds activation hook in `hvac-community-events.php` to call `hvac_ce_create_required_pages`. - The callback function checks for existing pages by slug and creates them using `wp_insert_post` if missing. Includes debug logging. Also fixes issues identified during E2E test debugging: - Corrects fatal error in `includes/community/class-login-handler.php` by replacing undefined constant `HVAC_COMMUNITY_EVENTS_PATH` with `HVAC_CE_PLUGIN_DIR`. - Updates `tests/e2e/tests/login.spec.ts` to use the correct selector `#wp-submit` for the login form submit button instead of `button[type="submit"]`. Documentation updates: - Adds `docs/automatic-page-creation-plan.md`. - Updates `README.md` regarding automatic page creation. - Updates Memory Bank files (`decisionLog.md`, `progress.md`, `activeContext.md`). Note: Activation hook logging did not appear during WP-CLI activation, requiring further investigation if page creation issues persist. E2E test confirmation pending.
61 lines
2.3 KiB
Markdown
61 lines
2.3 KiB
Markdown
# Version
|
|
|
|
Library for handling version information and constraints
|
|
|
|
[](https://travis-ci.org/phar-io/version)
|
|
|
|
## Installation
|
|
|
|
You can add this library as a local, per-project dependency to your project using [Composer](https://getcomposer.org/):
|
|
|
|
composer require phar-io/version
|
|
|
|
If you only need this library during development, for instance to run your project's test suite, then you should add it as a development-time dependency:
|
|
|
|
composer require --dev phar-io/version
|
|
|
|
## Version constraints
|
|
|
|
A Version constraint describes a range of versions or a discrete version number. The format of version numbers follows the schema of [semantic versioning](http://semver.org): `<major>.<minor>.<patch>`. A constraint might contain an operator that describes the range.
|
|
|
|
Beside the typical mathematical operators like `<=`, `>=`, there are two special operators:
|
|
|
|
*Caret operator*: `^1.0`
|
|
can be written as `>=1.0.0 <2.0.0` and read as »every Version within major version `1`«.
|
|
|
|
*Tilde operator*: `~1.0.0`
|
|
can be written as `>=1.0.0 <1.1.0` and read as »every version within minor version `1.1`. The behavior of tilde operator depends on whether a patch level version is provided or not. If no patch level is provided, tilde operator behaves like the caret operator: `~1.0` is identical to `^1.0`.
|
|
|
|
## Usage examples
|
|
|
|
Parsing version constraints and check discrete versions for compliance:
|
|
|
|
```php
|
|
|
|
use PharIo\Version\Version;
|
|
use PharIo\Version\VersionConstraintParser;
|
|
|
|
$parser = new VersionConstraintParser();
|
|
$caret_constraint = $parser->parse( '^7.0' );
|
|
|
|
$caret_constraint->complies( new Version( '7.0.17' ) ); // true
|
|
$caret_constraint->complies( new Version( '7.1.0' ) ); // true
|
|
$caret_constraint->complies( new Version( '6.4.34' ) ); // false
|
|
|
|
$tilde_constraint = $parser->parse( '~1.1.0' );
|
|
|
|
$tilde_constraint->complies( new Version( '1.1.4' ) ); // true
|
|
$tilde_constraint->complies( new Version( '1.2.0' ) ); // false
|
|
```
|
|
|
|
As of version 2.0.0, pre-release labels are supported and taken into account when comparing versions:
|
|
|
|
```php
|
|
|
|
$leftVersion = new PharIo\Version\Version('3.0.0-alpha.1');
|
|
$rightVersion = new PharIo\Version\Version('3.0.0-alpha.2');
|
|
|
|
$leftVersion->isGreaterThan($rightVersion); // false
|
|
$rightVersion->isGreaterThan($leftVersion); // true
|
|
|
|
```
|