Aura Component attributes
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
1
down vote
favorite
I have seen aura:component attributes like renderer and support.. But the following link does not mention these attributes..
Aura Component Doc
What am I missing here? Also what is the difference between global and public access specifier?
lightning
asked Nov 17 at 18:35
Akshit Gupta
343
add a comment |
up vote
1
down vote
favorite
I have seen aura:component attributes like renderer and support.. But the following link does not mention these attributes..
Aura Component Doc
What am I missing here? Also what is the difference between global and public access specifier?
lightning
asked Nov 17 at 18:35
Akshit Gupta
343
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have seen aura:component attributes like renderer and support.. But the following link does not mention these attributes..
Aura Component Doc
What am I missing here? Also what is the difference between global and public access specifier?
lightning
asked Nov 17 at 18:35
Akshit Gupta
343
I have seen aura:component attributes like renderer and support.. But the following link does not mention these attributes..
Aura Component Doc
What am I missing here? Also what is the difference between global and public access specifier?
lightning
lightning
asked Nov 17 at 18:35
Akshit Gupta
343
asked Nov 17 at 18:35
Akshit Gupta
343
asked Nov 17 at 18:35
Akshit Gupta
343
asked Nov 17 at 18:35
Akshit Gupta
343
asked Nov 17 at 18:35
Akshit Gupta
343
343
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
The documentation you linked describes the access specifiers:
[
access] Indicates whether the component can be used outside of its own namespace. Possible values are public (default), and global.
To be clear, a component must be global to be used outside of its own namespace. Components that are not part of a namespace you define have the pseudo-namespace c, as in c:myComponent.
The renderer is one of the elements of the Lightning component.
Based on your comment, it sounds like you're looking at the source view of some of the core Aura framework components. Note that neither attribute is documented as part of the public "shape" of a component even at the Aura level - they're internal to the framework.
In that context, support="GA" translates to "Generally Available". I can't say as I understand the Aura framework at a deep enough level to explain the mechanisms of the renderer attribute, but since it's connected to the server-side Java framework and not documented as part of the interface of an Aura or Lightning component, it's not something you have to deal with building your own Lightning components. The framework is responsible for "auto-wiring" your components' renderers, should you choose to create them, to ensure they're used appropriately.
answered Nov 17 at 18:50
David Reed
26.2k51645
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
The documentation you linked describes the access specifiers:
[
access] Indicates whether the component can be used outside of its own namespace. Possible values are public (default), and global.
To be clear, a component must be global to be used outside of its own namespace. Components that are not part of a namespace you define have the pseudo-namespace c, as in c:myComponent.
The renderer is one of the elements of the Lightning component.
Based on your comment, it sounds like you're looking at the source view of some of the core Aura framework components. Note that neither attribute is documented as part of the public "shape" of a component even at the Aura level - they're internal to the framework.
In that context, support="GA" translates to "Generally Available". I can't say as I understand the Aura framework at a deep enough level to explain the mechanisms of the renderer attribute, but since it's connected to the server-side Java framework and not documented as part of the interface of an Aura or Lightning component, it's not something you have to deal with building your own Lightning components. The framework is responsible for "auto-wiring" your components' renderers, should you choose to create them, to ensure they're used appropriately.
answered Nov 17 at 18:50
David Reed
26.2k51645
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
add a comment |
up vote
2
down vote
accepted
The documentation you linked describes the access specifiers:
[
access] Indicates whether the component can be used outside of its own namespace. Possible values are public (default), and global.
To be clear, a component must be global to be used outside of its own namespace. Components that are not part of a namespace you define have the pseudo-namespace c, as in c:myComponent.
The renderer is one of the elements of the Lightning component.
Based on your comment, it sounds like you're looking at the source view of some of the core Aura framework components. Note that neither attribute is documented as part of the public "shape" of a component even at the Aura level - they're internal to the framework.
In that context, support="GA" translates to "Generally Available". I can't say as I understand the Aura framework at a deep enough level to explain the mechanisms of the renderer attribute, but since it's connected to the server-side Java framework and not documented as part of the interface of an Aura or Lightning component, it's not something you have to deal with building your own Lightning components. The framework is responsible for "auto-wiring" your components' renderers, should you choose to create them, to ensure they're used appropriately.
answered Nov 17 at 18:50
David Reed
26.2k51645
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
The documentation you linked describes the access specifiers:
[
access] Indicates whether the component can be used outside of its own namespace. Possible values are public (default), and global.
To be clear, a component must be global to be used outside of its own namespace. Components that are not part of a namespace you define have the pseudo-namespace c, as in c:myComponent.
The renderer is one of the elements of the Lightning component.
Based on your comment, it sounds like you're looking at the source view of some of the core Aura framework components. Note that neither attribute is documented as part of the public "shape" of a component even at the Aura level - they're internal to the framework.
In that context, support="GA" translates to "Generally Available". I can't say as I understand the Aura framework at a deep enough level to explain the mechanisms of the renderer attribute, but since it's connected to the server-side Java framework and not documented as part of the interface of an Aura or Lightning component, it's not something you have to deal with building your own Lightning components. The framework is responsible for "auto-wiring" your components' renderers, should you choose to create them, to ensure they're used appropriately.
answered Nov 17 at 18:50
David Reed
26.2k51645
The documentation you linked describes the access specifiers:
[
access] Indicates whether the component can be used outside of its own namespace. Possible values are public (default), and global.
To be clear, a component must be global to be used outside of its own namespace. Components that are not part of a namespace you define have the pseudo-namespace c, as in c:myComponent.
The renderer is one of the elements of the Lightning component.
Based on your comment, it sounds like you're looking at the source view of some of the core Aura framework components. Note that neither attribute is documented as part of the public "shape" of a component even at the Aura level - they're internal to the framework.
In that context, support="GA" translates to "Generally Available". I can't say as I understand the Aura framework at a deep enough level to explain the mechanisms of the renderer attribute, but since it's connected to the server-side Java framework and not documented as part of the interface of an Aura or Lightning component, it's not something you have to deal with building your own Lightning components. The framework is responsible for "auto-wiring" your components' renderers, should you choose to create them, to ensure they're used appropriately.
answered Nov 17 at 18:50
David Reed
26.2k51645
edited Nov 17 at 19:04
answered Nov 17 at 18:50
David Reed
26.2k51645
answered Nov 17 at 18:50
David Reed
26.2k51645
answered Nov 17 at 18:50
David Reed
26.2k51645
26.2k51645
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
add a comment |
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
link defines support inside aura component.. Thanks for your answer
– Akshit Gupta
Nov 17 at 18:55
add a comment |
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%2fsalesforce.stackexchange.com%2fquestions%2f239729%2faura-component-attributes%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
