Apa fungsi plugin xdebug sublime

Table of Contents Show

Getting started
Setting up Xdebug
Setting up Sublime Text 3
Start the Xdebug session
Breakpoints
Video yang berhubungan

Sublime Text 3 merupakan text editor yang sangat powerful untuk menulis code dalam pengembangan sebuah aplikasi. Jadi jangan heran banyak programmers yang menyukai text editor yang satu ini. selain tampilannya yang simple, Sublime Text 3 ini sangat fleksibel. Dengan dukungan plugins yang sangat banyak, text editor yang satu ini juga mendukung banyak bahasa pemrograman seperti C, C++, C#, PHP, CSS, HTML, ASP dan banyak lagi. Pada artikel kali ini, saya akan menjelaskan packages/plugins yang saya gunakan untuk mendukung pengembangan aplikasi berbasis web dengan bahasa pembrograman PHP. Berikut daftar pluginnya:

1. Package Control

Dengan package ini, kita dengan mudah menginstal packages/plugins yang kita perlukan.

2. SublimeCodeIntel

Package yang selalu saya gunakan. Package ini bertugas untuk memberikan petunjuk yang berkaitan dengan fungsi, objek, nama variabel, dan lain-lain. Package ini juga bisa menunjukkan methods dan parameters apa yang tersedia di dalam objects/classes. Package ini pada dasarnya merupakan plugin Komodo CodeIntel dan kadang-kadang bermasalah. tapi sebagian besar berjalan lancar.

3. SublimeLinter

Package ini sangat membantu saya. Package ini terus menerus melihat apa yang saya tulis dan dengan mudah memberitahukan kepada saya jika ada yang salah, contohnya jika saya lupa menuliskan titik koma atau tutup kurung kurawal.

Untuk versi 3 ke atas, SublimeLinter telah menjadi modular. artinya, anda harus menginstal package utama terlebih dahulu, lalu plugin/module untuk setiap bahasa yang kamu butuhkan. Tiap plugin memiliki setingan tersendiri yang di perlukan. jadi harap kalian membaca terlebih dahulu. Untuk pengembangan PHP dan JavaScript , saya menggunakan:
4. SideBarEnhancements Menyediakan fitur tambahan saat melakukan klik kanan pada elements (files/folders) di sidebar. Plugin yang sangat memudahkan kita.

5. PhpDoc

Sebagai good programmer, kita harus mendokumentasikan atau memberikan keterangan di setiap function/method atau class yang kita buat. Plugin ini akan membantu anda mendokumentasikan docblocks untuk PHPDocumentor.

6. TrailingSpaces

PHP memang mengabaikan setiap empty space yang ada di setiap baris. Tapi kadang kita merasa sangat menggangu jika terdapat beberapa empty space di akhir baris code. Plugin ini sangat berguna untuk menemukan jika terdapat empty space yang tidak diperlukan.

7. BracketHighlighter

Sublime Text 3 memang sudah mempunyai fitur untuk memberi tanda pada setiap pasangan bracket yang di tunjuk. Tapi plugin yang satu ini akan sangat membantu anda, karena terdapat beberapa fitur tambahan agar setiap bracket yang di pilih terlihat lebih jelas.

8. Sublime Function Name Display

Plugin yang satu ini akan menampilkan nama function/method di bagian bar bagian bawah ketika cursor kita ditempatkan di function/method tersebut. Berikut plugin-plugin pendukung atau optional yang berguna dan bisa anda coba:

1 . VCS Gutter

Jika kamu menggunakan Git dan Mercurial, plugins ini memberikan informasi real-time tentang apa yang berubah, ditambahkan atau dihapus di file terakhir.

2. SFTP, Berbayar

Jika kamu menggunakan SFTP, FTP, dan FTPS. Anda bisa menggunakan paket ini. Paket ini mendukung remote folder browsing, editing dan synchronization antara lokal dan remote files.

3. Tortoise (Kusus Windows)

Saya menggunakan ini sebagai package pendukung untuk SideBarGit. package ini tidak memiliki banya fitur, tapi package ini sangat membantu. Jika kamu menyukai Tortoise Git tapi bekerja di OS Linux, kalian bisa mencoba menggunakan RabbitVCS.

4. sublimegithub

Semua developer seharusnya menggunakan code snippets. Saya menggunakan Gist yang disediakan GitHub dan package ini membuat saya menggunakannya dengan mudah (save/paste).

5. Phpcs

Package ini akan menambahkan dukungan untuk PHP_CodeSniffer ke Sublime Text 2. package ini akan mengecek jika code yang ada tulis merupakan salah satu aturan standard. Pilih salah satu: Zend, PEAR.. dan banyak lagi. kamu bisa melihat lebih lanjut di website PHP_CodeSniffer untuk detail konfigurasinya.

6. Xdebug Client

Yang terakhir, Xdebug client favorit saya untuk Sublime Text 3. Tool ini berjalan sangat lancar dan mengijinkan untuk menggunakan semua kemampuan debugging Xdebug.

Saya menggunakan kode berikut:

register_setting( 'myplugin_options', //setting group name 'myplugin_options', //option name that will be stored in the database 'myplugin_validate_options'//optional callback function ); function myplugin_validate_options($input) { //how can i print $input to the screen or view the output of this function for debugging purpsoses? }

Saya hanya perlu tahu bagaimana kita bisa men-debug fungsi panggilan balik validasi kami. Dari apa yang saya lihat mereka tidak dapat di-output ke layar sehingga membuat penulisan kode yang benar di dalamnya menjadi sulit.

Terima kasih.

Debugging – we all do it a lot. Writing code perfectly the first time around is hard and only a few (if any) succeed at it. More than a year ago, Shameer wrote an article on SitePoint about how you can debug your application using Xdebug and Netbeans. In this article, we are going to have a look at how we can debug using Xdebug in combination with Sublime Text.

Getting started

First of all, we need to have the PHP Xdebug extension installed. If you are uncertain on how to get this done, please have a look at the link provided in the introduction. Make sure that Xdebug is working by checking if it’s listed in your phpinfo().
Of course we also need Sublime Text. I will be using the latest version: Sublime Text 3. It should also work with Sublime Text 2.

Setting up Xdebug

We need to configure xdebug by adding the following to your php.ini file, or even better, to an xdebug.ini file as described here under How-to On Linux.

xdebug.remote_enable=1 xdebug.remote_handler=dbgp xdebug.remote_host=127.0.0.1 xdebug.remote_port=9000 xdebug.remote_log="/var/log/xdebug/xdebug.log"

In general you will be using 127.0.0.1 as your host. However, If you are using vagrant for example, you will be using something like 10.0.2.2, depending on where Xdebug can find your system.

The remote log is not necessary, but in case of problems, it’s the place where you can find information about errors that occurred.

Don’t forget to restart your webserver!

Setting up Sublime Text 3

One of the strengths of Sublime is the fact that you can extend it easily with packages. In this case, we are going to install the Xdebug package. If you haven’t done so already, make sure you can install packages by installing package control.

Once you have the package control installed, you should start Sublime Text 3. Open up the command palette from the tools menu and search for “install package”.

Now you can search for any package you like. In our case, we are going to search for the package “Xdebug client”.

The last bit we have to do is set up the project within Sublime. The easiest way to do this is to open up the root directory of your application, go to projects and click on “save projects as”. I suggest you save the file within the root of your application, so you can save it in your version control system if you are using any and you can configure it easily at all times.

Open up the just created project file. The content will look like this:

{ "folders": [ { "follow_symlinks": true, "path": "." } ] }

We are going to add a few more lines:

{ "folders": [ { "follow_symlinks": true, "path": "." } ], "settings": { "xdebug": { "url": "http://my.local.website/", } } }

As you can see, I only added a URL to my actual web application. I could set more settings for Xdebug, however, this is enough to start with. I could have also set this URL in the Xdebug settings itself, but in that case, I couldn’t work on multiple projects without having to change the Xdebug config each time.

Start the Xdebug session

We can now start the Xdebug session to see if everything is set up properly. In the menu, click on tools -> Xdebug and click on start debugging (launch browser). You will notice that your website is opened up and that ?XDEBUG_SESSION_START=sublime.xdebug is added to the end of the URL. This will start the xdebug session. In Sublime, some extra panels appear where debug information will be shown, after you have set one or more breakpoints.

Breakpoints

Let’s set out first breakpoint. A breakpoint is basically a flag where your application will halt when it reaches it. At the moment it halts, you can inspect all the variables’ values so you know actually what is going on.

We can add a breakpoint by clicking with our right mouse on a line, going to Xdebug and then clicking on add/remove breakpoint. A marker will be added to the line gutter to indicate that a breakpoint has been set.

We open up our browser again and continue with the session we just started. You will notice that as soon as you go to the page where the breakpoint is, the page will stop loading. If you now open up Sublime, you will see a lot of information shown in the Xdebug panels.

The Xdebug stack and Xdebug context are very interesting. In the stack, you can see the whole stacktrace your call went through.

In the context, you will see all global variables, but also the variables you defined yourself. You can click on these variables to see exactly these variables are holding. For instance, in the screenshot below, I clicked on the $_SERVER variable.

Notice that a yellow arrow is pointing at the line the application is currently halted on.

So our application halted and now we can look through the variables defined. However, we are done and we want to move on. What now? When you right mouse click once again and hover over the Xdebug menu, you will have several options:

Run Which will run the application until the next breakpoint or until the ending.
Run to line which will run until the line you clicked.
Step into will step into the current function and stops right after.
Step over Will step over the current function and stops right after.
Step out Will step out of the current function and stop right after.
Stop Will stop debugging.
Detach Will also stop debugging.

Run and stop are quite easy to understand. The step methods could be a little confusing. Let’s dive into these with a simple example.

Class Foo() { public function bar(Array $arr) { $arr = self::fooBar($arr); // Breakpoint return $arr; } public function fooBar(Array $arr) { return array_values($arr); } }

Imagine you added a breakpoint to the first line of the method bar. So on the line with the breakpoint comment (// breakpoint).

With step into, the debugger will step into the fooBar method and will stop there at the first line. So in this case, the debugger will halt on the return array_values($arr); line.

Step over will call the method, but will not stop. It will stop at the next line available after calling the method. So in this case, it will stop at return $arr;

Lastly, with step out it will run through the whole bar method and return to the caller. In this case, it will go out of the object, back to the original caller.

If you just decide to run, the application will run further until the moment it is done executing or another breakpoint occurs.

Conclusion

In this article we saw how we could integrate Xdebug with Sublime and made sure we understood how to debug. Almost every IDE suitable for PHP can integrate with Xdebug. If you are interested in debugging like this in Netbeans, have a look at the article mentioned in the introduction. Are you using breakpoints? Or are you using PHP functions like var_dump to get your debug data? Let us know in the comments below!