Reputation
747
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
6 26
Impact
~32k people reached

  • 0 posts edited
  • 4 helpful flags
  • 148 votes cast
Jan
24
comment Using Travis CI to run unit tests and running phpunit locally
I suppose there's also the advantage of having a clean commit history. If a build fails locally, then you can fix before committing
Jan
23
comment Using Travis CI to run unit tests and running phpunit locally
Aside from the wait time, are there any more advantages of running phpunit locally?
Jan
23
comment Using Travis CI to run unit tests and running phpunit locally
Thanks for the insight @J.D.
Jan
22
accepted How best to display notifications on the front-end using caught exceptions as an example
Jan
22
asked Logging error messages with error_log() and WP_DEBUG_LOG
Jan
22
comment How best to display notifications on the front-end using caught exceptions as an example
wp_head is triggered in the <head> section. I think notification messages should be displayed in the body? But I'm now thinking which body template hook is guaranteed to always be there?
Jan
22
asked How best to display notifications on the front-end using caught exceptions as an example
Jan
6
accepted How to rename the wp-config.php file once under version control?
Jan
6
comment How to rename the wp-config.php file once under version control?
Thanks @bosco, that's nicely clarified what should be done.
Jan
6
asked How to rename the wp-config.php file once under version control?
Jan
6
accepted Using Travis CI to run unit tests and running phpunit locally
Jan
6
comment Why include a composer.json file with my plugin?
+1 from me for giving me these things to think about :)
Jan
6
accepted Why include a composer.json file with my plugin?
Jan
6
comment Why include a composer.json file with my plugin?
Thank you for such a detailed summary.
Jan
5
asked Using Travis CI to run unit tests and running phpunit locally
Jan
2
comment Why include a composer.json file with my plugin?
If I use the psr-4 key in composer.json, Composer generates a vendor/autoload.php file, which I suppose I could commit to the wp.org repo. spl_autoload_register() is used instead of __autoload() so if anyone else authoring a plugin does the same there shouldn't be conflicts.
Jan
2
comment Why include a composer.json file with my plugin?
Thanks @birgire. In my particular case, my plugin has no dependencies so there's less of a need to provide a composer.json file as a "readme" for developers. I was thinking more along the lines of using composer.json purely for the autoloading capabilities. Is this a common thing to do? I'm wondering if you have any thoughts on that? Thanks again.
Jan
2
asked Why include a composer.json file with my plugin?
Dec
31
awarded  Nice Question
Dec
31
comment Why is it necessary to prevent direct access to included files?
Thanks for the edit. So are you saying if a file's code is designed with security in mind, the ABSPATH check is redundant (WordPress core files being an example of this)?