| [ Index ] |
PHP Cross Reference of Phabricator |
[Source view] [Print] [Project Stats]
(no description)
| File Size: | 101 lines (3 kb) |
| Included or required: | 0 times |
| Referenced: | 0 times |
| Includes or requires: | 0 files |
| setRenderWithImpliedContext($render_with_implied_context) X-Ref |
| Render story text using contextual language to identify the object the story is about, instead of the full object name. For example, without contextual language a story might render like this: alincoln created D123: Chop Wood for Log Cabin v2.0 With contextual language, it will render like this instead: alincoln created this revision. If the interface where the text will be displayed is specific to an individual object (like Asana tasks that represent one review or commit are), it's generally more natural to use language that assumes context. If the target context may show information about several objects (like JIRA issues which can have several linked revisions), it's generally more useful not to assume context. param: bool True to assume object context when rendering. return: this |
| getRenderWithImpliedContext() X-Ref |
| Determine if rendering should assume object context. For discussion, see @{method:setRenderWithImpliedContext}. return: bool True if rendering should assume object context is implied. |
| setFeedStory(PhabricatorFeedStory $feed_story) X-Ref |
| No description |
| getFeedStory() X-Ref |
| No description |
| setViewer(PhabricatorUser $viewer) X-Ref |
| No description |
| getViewer() X-Ref |
| No description |
| willPublishStory($object) X-Ref |
| Hook for publishers to mutate the story object, particularly by loading and attaching additional data. |
| getStoryText($object) X-Ref |
| No description |
| Generated: Sun Nov 30 09:20:46 2014 | Cross-referenced by PHPXref 0.7.1 |