mirror of
https://we.phorge.it/source/phorge.git
synced 2024-12-23 22:10:55 +01:00
Correct spelling of "phabrictor" in Lipsum and elsewhere
Summary: Ref T12319. The product name is misspelled in some methods, and a few places in the documentation. Test Plan: `grep` Reviewers: chad Reviewed By: chad Maniphest Tasks: T12319 Differential Revision: https://secure.phabricator.com/D17419
This commit is contained in:
parent
be785d1e8a
commit
1b2c047ce0
9 changed files with 14 additions and 17 deletions
|
@ -8,7 +8,7 @@ final class PhabricatorDifferentialRevisionTestDataGenerator
|
|||
}
|
||||
|
||||
public function generateObject() {
|
||||
$author = $this->loadPhabrictorUser();
|
||||
$author = $this->loadPhabricatorUser();
|
||||
|
||||
$revision = DifferentialRevision::initializeNewRevision($author);
|
||||
$revision->attachReviewerStatus(array());
|
||||
|
@ -39,7 +39,7 @@ final class PhabricatorDifferentialRevisionTestDataGenerator
|
|||
public function getCCPHIDs() {
|
||||
$ccs = array();
|
||||
for ($i = 0; $i < rand(1, 4);$i++) {
|
||||
$ccs[] = $this->loadPhabrictorUserPHID();
|
||||
$ccs[] = $this->loadPhabricatorUserPHID();
|
||||
}
|
||||
return $ccs;
|
||||
}
|
||||
|
|
|
@ -8,7 +8,7 @@ final class PhabricatorFileTestDataGenerator
|
|||
}
|
||||
|
||||
public function generateObject() {
|
||||
$author_phid = $this->loadPhabrictorUserPHID();
|
||||
$author_phid = $this->loadPhabricatorUserPHID();
|
||||
$dimension = 1 << rand(5, 12);
|
||||
$image = id(new PhabricatorLipsumMondrianArtist())
|
||||
->generate($dimension, $dimension);
|
||||
|
|
|
@ -89,9 +89,6 @@ abstract class PhabricatorTestDataGenerator extends Phobject {
|
|||
return $xaction;
|
||||
}
|
||||
|
||||
|
||||
|
||||
|
||||
public function loadOneRandom($classname) {
|
||||
try {
|
||||
return newv($classname, array())
|
||||
|
@ -106,11 +103,11 @@ abstract class PhabricatorTestDataGenerator extends Phobject {
|
|||
}
|
||||
}
|
||||
|
||||
public function loadPhabrictorUserPHID() {
|
||||
public function loadPhabricatorUserPHID() {
|
||||
return $this->loadOneRandom('PhabricatorUser')->getPHID();
|
||||
}
|
||||
|
||||
public function loadPhabrictorUser() {
|
||||
public function loadPhabricatorUser() {
|
||||
return $this->loadOneRandom('PhabricatorUser');
|
||||
}
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ final class PhabricatorManiphestTaskTestDataGenerator
|
|||
}
|
||||
|
||||
public function generateObject() {
|
||||
$author_phid = $this->loadPhabrictorUserPHID();
|
||||
$author_phid = $this->loadPhabricatorUserPHID();
|
||||
$author = id(new PhabricatorUser())
|
||||
->loadOneWhere('phid = %s', $author_phid);
|
||||
$task = ManiphestTask::initializeNewTask($author)
|
||||
|
@ -63,7 +63,7 @@ final class PhabricatorManiphestTaskTestDataGenerator
|
|||
public function getCCPHIDs() {
|
||||
$ccs = array();
|
||||
for ($i = 0; $i < rand(1, 4);$i++) {
|
||||
$ccs[] = $this->loadPhabrictorUserPHID();
|
||||
$ccs[] = $this->loadPhabricatorUserPHID();
|
||||
}
|
||||
return $ccs;
|
||||
}
|
||||
|
@ -83,7 +83,7 @@ final class PhabricatorManiphestTaskTestDataGenerator
|
|||
if (rand(0, 3) == 0) {
|
||||
return null;
|
||||
} else {
|
||||
return $this->loadPhabrictorUserPHID();
|
||||
return $this->loadPhabricatorUserPHID();
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ final class PhabricatorPholioMockTestDataGenerator
|
|||
}
|
||||
|
||||
public function generateObject() {
|
||||
$author_phid = $this->loadPhabrictorUserPHID();
|
||||
$author_phid = $this->loadPhabricatorUserPHID();
|
||||
$author = id(new PhabricatorUser())
|
||||
->loadOneWhere('phid = %s', $author_phid);
|
||||
$mock = PholioMock::initializeNewMock($author);
|
||||
|
@ -82,7 +82,7 @@ final class PhabricatorPholioMockTestDataGenerator
|
|||
public function getCCPHIDs() {
|
||||
$ccs = array();
|
||||
for ($i = 0; $i < rand(1, 4);$i++) {
|
||||
$ccs[] = $this->loadPhabrictorUserPHID();
|
||||
$ccs[] = $this->loadPhabricatorUserPHID();
|
||||
}
|
||||
return $ccs;
|
||||
}
|
||||
|
|
|
@ -55,7 +55,7 @@ this document. See @{article:Adding New CSS and JS}.)
|
|||
phabricator/webroot/rsrc/css/application/derp/
|
||||
|
||||
These directories under `phabricator/src/applications/derp/` represent
|
||||
the basic set of class types from which most Phabrictor applications are
|
||||
the basic set of class types from which most Phabricator applications are
|
||||
assembled. Each would contain a class file. For `Derp`, these classes could be
|
||||
something like:
|
||||
|
||||
|
|
|
@ -79,7 +79,7 @@ a config like this:
|
|||
To select a configuration file, write the name of the file (relative to
|
||||
`phabricator/conf/`) to `phabricator/conf/local/ENVIRONMENT`. For example, to
|
||||
select `phabricator/conf/custom/exampleconfig.conf.php`, you would write
|
||||
"custom/exampleconfig" to `phabrictor/conf/local/ENVIRONMENT`:
|
||||
"custom/exampleconfig" to `phabricator/conf/local/ENVIRONMENT`:
|
||||
|
||||
phabricator/ $ echo custom/exampleconfig > conf/local/ENVIRONMENT
|
||||
phabricator/ $ cat conf/local/ENVIRONMENT
|
||||
|
|
|
@ -59,7 +59,7 @@ a typical audit workflow:
|
|||
- Alice publishes a commit containing some Javascript.
|
||||
- This triggers an audit request to Bailey, the Javascript technical
|
||||
lead on the project (see below for a description of trigger mechanisms).
|
||||
- Later, Bailey logs into Phabrictor and sees the audit request. She ignores
|
||||
- Later, Bailey logs into Phabricator and sees the audit request. She ignores
|
||||
it for the moment, since it isn't blocking anything. At the end of the
|
||||
week she looks through her open requests to see what the team has been
|
||||
up to.
|
||||
|
|
|
@ -37,7 +37,7 @@ only members of the "Backend" project, nor does it allow them to see it if they
|
|||
otherwise could not. Likewise, removing projects does not affect visibility.
|
||||
|
||||
If you're familiar with other software that works differently, this may be
|
||||
unexpected, but the rule in Phabrictor is simple: **adding and removing
|
||||
unexpected, but the rule in Phabricator is simple: **adding and removing
|
||||
projects never affects policies.**
|
||||
|
||||
Note that you //can// write policy rules which restrict capabilities to members
|
||||
|
|
Loading…
Reference in a new issue