-
|
Is the origin for writing an action the name of the component or the component itself? For instance, if the action originates in the grid do I write grid or since the grid is named "core" do I write core? 
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
|
It is the name of the component in most cases. In the case of Emit from a
Method it is the name of the Method.
…On Tue, Oct 24, 2023 at 9:54 AM Andrea Etkie ***@***.***> wrote:
Is the origin for writing an action the name of the component or the
component itself?
For instance, if the action originates in the grid do I write *grid* or
since the grid is named "core" do I write *core*?
[image: Screenshot 2023-10-24 at 9 54 21 AM]
<https://user-images.githubusercontent.com/113473933/277681991-8758c74a-41d8-46c2-afd2-32baf61074dc.png>
—
Reply to this email directly, view it on GitHub
<#227>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQK7BP56SXYOEO7TV2KS3YA7CCZAVCNFSM6AAAAAA6NXZJW6VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZVG43TENJTHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I think this is a good reason in examples to NOT name the component what the component is. So in examples avoiding calling the grid grid and doing what you have done and naming it core. It is why the display window does nothing until you give it a name, then you can prescribe actions to it using whatever you named it (which of course I tend to name it display...) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, helpful! Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I'm thinking we should change the default names. Right now the default name
for the Grid is grid simply because I didn't think about it. Maybe the
default name should be "a grid"? or "Grid 17" where the number is different
for each grid?
…On Tue, Oct 24, 2023 at 1:18 PM Andrea Etkie ***@***.***> wrote:
Yes, helpful! Thanks
—
Reply to this email directly, view it on GitHub
<#227 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQK7HIZHRSYAXUR7FGOZTYA7Z7HAVCNFSM6AAAAAA6NXZJW6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TGNZSGY4TE>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I like the number idea. For a design I was working on with multiple grids I started naming them "grid first", "grid second" etc because I knew they needed to stay in a certain order and when collapsed, I was losing sight of the order if calling them "grid core", "grid emotions" etc. |
Beta Was this translation helpful? Give feedback.
I think this is a good reason in examples to NOT name the component what the component is. So in examples avoiding calling the grid grid and doing what you have done and naming it core.
It is why the display window does nothing until you give it a name, then you can prescribe actions to it using whatever you named it (which of course I tend to name it display...)