Yii2 preferred way to set 'class'
In Yii2 codebase, I saw 2 different types of config declaration:
One way with CLASS_NAME::class
'options' => ['class' => OptionsAction::class],
Another way with full string representation
'options' => ['class' => 'yiirestOptionsAction'],
Which way is preferable and why?
php yii2
add a comment |
In Yii2 codebase, I saw 2 different types of config declaration:
One way with CLASS_NAME::class
'options' => ['class' => OptionsAction::class],
Another way with full string representation
'options' => ['class' => 'yiirestOptionsAction'],
Which way is preferable and why?
php yii2
I've seen both, but am using ::class since it is refactor friendly.
– Isitar
Nov 23 '18 at 8:14
add a comment |
In Yii2 codebase, I saw 2 different types of config declaration:
One way with CLASS_NAME::class
'options' => ['class' => OptionsAction::class],
Another way with full string representation
'options' => ['class' => 'yiirestOptionsAction'],
Which way is preferable and why?
php yii2
In Yii2 codebase, I saw 2 different types of config declaration:
One way with CLASS_NAME::class
'options' => ['class' => OptionsAction::class],
Another way with full string representation
'options' => ['class' => 'yiirestOptionsAction'],
Which way is preferable and why?
php yii2
php yii2
edited Nov 23 '18 at 13:36
akshaypjoshi
5371216
5371216
asked Nov 23 '18 at 8:12
Dmitry Ermichev
6917
6917
I've seen both, but am using ::class since it is refactor friendly.
– Isitar
Nov 23 '18 at 8:14
add a comment |
I've seen both, but am using ::class since it is refactor friendly.
– Isitar
Nov 23 '18 at 8:14
I've seen both, but am using ::class since it is refactor friendly.
– Isitar
Nov 23 '18 at 8:14
I've seen both, but am using ::class since it is refactor friendly.
– Isitar
Nov 23 '18 at 8:14
add a comment |
1 Answer
1
active
oldest
votes
Both ways might be used, but the better way is the declaration with help ::class
because:
- it makes dependencies more clear. All dependencies will declare one place - in USE section.
- it makes an ability to validation of code with help IDE. If there is a class name in a string then IDE can't analyze this string and it means IDE can't validate your code
- it makes refactoring of existing code more usability. If all dependencies will declare in one place and they won't be contained in strings you won't look for a necessary declaration of a class name in all code and you can apply tools of your IDE to code refactoring
In addition - using::class
does not trigger autoloading.
– Bizley
Nov 23 '18 at 9:58
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53442829%2fyii2-preferred-way-to-set-class%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Both ways might be used, but the better way is the declaration with help ::class
because:
- it makes dependencies more clear. All dependencies will declare one place - in USE section.
- it makes an ability to validation of code with help IDE. If there is a class name in a string then IDE can't analyze this string and it means IDE can't validate your code
- it makes refactoring of existing code more usability. If all dependencies will declare in one place and they won't be contained in strings you won't look for a necessary declaration of a class name in all code and you can apply tools of your IDE to code refactoring
In addition - using::class
does not trigger autoloading.
– Bizley
Nov 23 '18 at 9:58
add a comment |
Both ways might be used, but the better way is the declaration with help ::class
because:
- it makes dependencies more clear. All dependencies will declare one place - in USE section.
- it makes an ability to validation of code with help IDE. If there is a class name in a string then IDE can't analyze this string and it means IDE can't validate your code
- it makes refactoring of existing code more usability. If all dependencies will declare in one place and they won't be contained in strings you won't look for a necessary declaration of a class name in all code and you can apply tools of your IDE to code refactoring
In addition - using::class
does not trigger autoloading.
– Bizley
Nov 23 '18 at 9:58
add a comment |
Both ways might be used, but the better way is the declaration with help ::class
because:
- it makes dependencies more clear. All dependencies will declare one place - in USE section.
- it makes an ability to validation of code with help IDE. If there is a class name in a string then IDE can't analyze this string and it means IDE can't validate your code
- it makes refactoring of existing code more usability. If all dependencies will declare in one place and they won't be contained in strings you won't look for a necessary declaration of a class name in all code and you can apply tools of your IDE to code refactoring
Both ways might be used, but the better way is the declaration with help ::class
because:
- it makes dependencies more clear. All dependencies will declare one place - in USE section.
- it makes an ability to validation of code with help IDE. If there is a class name in a string then IDE can't analyze this string and it means IDE can't validate your code
- it makes refactoring of existing code more usability. If all dependencies will declare in one place and they won't be contained in strings you won't look for a necessary declaration of a class name in all code and you can apply tools of your IDE to code refactoring
edited Nov 23 '18 at 8:57
answered Nov 23 '18 at 8:20
Maxim Fedorov
2,905419
2,905419
In addition - using::class
does not trigger autoloading.
– Bizley
Nov 23 '18 at 9:58
add a comment |
In addition - using::class
does not trigger autoloading.
– Bizley
Nov 23 '18 at 9:58
In addition - using
::class
does not trigger autoloading.– Bizley
Nov 23 '18 at 9:58
In addition - using
::class
does not trigger autoloading.– Bizley
Nov 23 '18 at 9:58
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53442829%2fyii2-preferred-way-to-set-class%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I've seen both, but am using ::class since it is refactor friendly.
– Isitar
Nov 23 '18 at 8:14