ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

PHP Companion

by erichard ST3

A Sublime Text 3 plugin that provides cool stuff for PHP 5.3+ coding session.

Details

Installs

  • Total 110K
  • Win 57K
  • OS X 28K
  • Linux 25K
Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6
Windows 28 63 82 83 84 63 59 52 63 70 90 91 68 51 45 77 90 72 71 46 37 50 63 80 74 64 44 35 41 68 67 77 69 70 51 42 58 65 76 58 70 50 50 74 58 98
OS X 9 26 18 32 30 17 27 16 23 35 20 19 23 14 14 26 28 24 21 13 10 16 19 21 17 11 14 14 18 21 25 24 20 23 13 14 20 23 25 29 31 16 13 32 24 38
Linux 3 29 29 32 26 30 24 18 29 46 31 25 38 22 20 24 28 31 35 18 21 19 20 21 21 26 17 15 14 21 24 34 30 30 20 20 31 27 28 24 34 12 24 23 25 34

Readme

Source
raw.​githubusercontent.​com

Gitter

Sublime PHP Companion

This Sublime Text 3 Package provides cool stuff for PHP 5.3+ coding session.

Successor of SublimeCTagsPHP

This plugin is the successor of SublimeCTagsPHP. PHP Companion uses the built-in index of Sublime Text 3 instead of CTags.

Warning! PHP Companion does not work on Sublime Text 2 and never will.

Installation

Package control

Just search for PHP Companion in package control and you're ready.

Keybinding

The package no longer provides keybindings. You will have to install your own shortcuts. The Default.sublime-keymap-sample will give you the shortcuts I personally use.

Commands

find_use

Just bring your cursor hover a class name, hit the F5 key (personal shortcut) and that's it.

It will show you the different namespace that match your class, pick up one and you're done.

PHP Companion will sort your uses statement in alphabetical order. This can be configured to sort by line length with the use_sort_length user setting.

expand_fqcn

This command expands the class under the cursor to its FQCN (Fully Qualified Class Name). You have two keys for this command F6 and shift+F6 (personal shortcut) that respectively expand with and without the leading namespace separator \.

import_namespace

Just hit the F4 key (personal shortcut), it will add the namespace definition based on the absolute filename of the current file. I use a simple trick to determine where the namespace begun, actually the namespace will start at the first CamelCased folder.

If a namespace is already declared, the command will shout how crazy you are in the status bar.

Warning: This feature requires a filename so the command won't work in an unsaved buffer.

goto_definition_scope

Hit shift+F12 (personal shortcut) to search for a method definition based on the current scope. It will fallback to the “goto_definition” command if a match was not found.

insert_php_constructor_property

Hit F7 (personal shortcut) to insert both a constructor argument and its according property. The property will be private by default but you can change it with the visibility setting.

implement

Place your cursor on a class, abstract class or an interface name and hit the F3 key (personal shortcut). Matching interfaces or classes will be shown. Select one and then import all or one of the methods from that interface or class.

See use_todo_implement setting.

Settings

Settings can be stored either in your system wide “PHP Companion.sublime-settings” file or in the project settings file. This allows you to set preferences per-project if you need to.

If you're storing settings in a project file, put them in a phpcompanion node like this:

"phpcompanion": {
    "namespace_prefix": "VendorName\Project\Foo\Bar",
    "exclude_dir": [
        "vendor",
        "build"
    ]
}

exclude_dir

List of directories to exclude when searching for the class declaration file. Path is relative to the project directory.

Please note that the filtering is done after the search in the index. So this option has no impact on performance, it's just a convenient way to avoid duplicate namespace declaration in some case.

start_dir_pattern

The pattern used to guess the namespace in the import_namespace command. The default pattern should work for most uses cases but you can change it if your projects are stored in different way.

namespace_prefix

If you have a namespace which is not fully exposed by the file path, you can set a namespace prefix. For example, suppose you have a class in

src/Foo/Bar.php

adding a namespace_prefix of 'Vendor\Project' would result in a resolved namespace declaration of

namespace Vendor\Project\Foo;

use_sort_length

When importing use statements with the find_use command, sort statements by the length of the line.

use_todo_implement

When an interface or abstract class is implemented, this option is used to customize the method body of the newly added methods.

The available options are true and false.

"use_todo_implement": true: “ public function methodName() { // TODO: Implement 'methodName' method. }

`"use_todo_implement": false`:

public function methodName() { throw new \Exception("Method 'methodname' not implemented”); }

## Licence

All of Sublime PHP Companion is licensed under the MIT license.

  Copyright (c) 2013 Erwan Richard <erwann.richard@gmail.com>

  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
  in the Software without restriction, including without limitation the rights
  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  copies of the Software, and to permit persons to whom the Software is
  furnished to do so, subject to the following conditions:

  The above copyright notice and this permission notice shall be included in
  all copies or substantial portions of the Software.

  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
  THE SOFTWARE.