require vs require_once #222
Comments
|
Great point - this is something that will be resolved. |
NikV
added a commit
to NikV/WordPress-Plugin-Boilerplate
that referenced
this issue
Nov 4, 2014
See : DevinVinson#222. I believe this was in favor of doing it "correctly"?
|
Bump - suggest closing this issue now that #231 is merged 😄 |
azuredevil0818
pushed a commit
to azuredevil0818/WordPress-Plugin-Boilerplate
that referenced
this issue
Jul 18, 2023
See : DevinVinson/WordPress-Plugin-Boilerplate#222. I believe this was in favor of doing it "correctly"?
harry908nilson
pushed a commit
to marcolane/wordpress
that referenced
this issue
Sep 1, 2023
See : DevinVinson/WordPress-Plugin-Boilerplate#222. I believe this was in favor of doing it "correctly"?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is very minor, but it's the first thing I would change when using this boilerplate ...
require_once() is used in the main plugin file, but I'm not seeing any reason to do that there. Typically, you use that when there is a possibility of a file being loaded twice. That is not possible with a main plugin file, therefore it should use a plain old require() instead.
Technically it's a smidgeon faster, but the main reason for doing it that way is just to make it more "correct".
The text was updated successfully, but these errors were encountered: