docs icon indicating copy to clipboard operation
docs copied to clipboard

4/8 review of the properties page

Open rlasjunies opened this issue 5 years ago • 2 comments

The previous content on the "## Memory/speed overhead of using Properties" is maintained as is

rlasjunies avatar May 08 '20 16:05 rlasjunies

Yes, we could say something more along the lines of “It’s good practice to divide up your application into multiple components and split them across different files. As your application becomes larger, this quickly becomes essential.”

On 9 May 2020, at 17:50, Richard Lasjunies [email protected] wrote:

@rlasjunies commented on this pull request.

In src/concepts/components/properties.md https://github.com/yewstack/docs/pull/85#discussion_r422519064:


Properties

-Properties enable child and parent components to communicate with each other. +It is a common need to receive data from the parent component using properties. Not sure it's necessary to have "as an application becomes more complex, it becomes necessary to split it up into many different components to achieve an effective separation of concerns." In some way it should be the introduction of Components.

Anyway, I paste your whole proposal.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yewstack/docs/pull/85#discussion_r422519064, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKFSTPKV42ZVIXTQFFFMW7TRQWCV3ANCNFSM4M4JYSSQ.

teymour-aldridge avatar May 09 '20 16:05 teymour-aldridge

Ok.

On 9 May 2020, at 18:14, Richard Lasjunies [email protected] wrote:

@rlasjunies commented on this pull request.

In src/concepts/components/properties.md https://github.com/yewstack/docs/pull/85#discussion_r422521643:

-{% hint style="info" %} -Types for which you derive Properties must also implement Clone. This can be done by either using #[derive(Properties, Clone) or manually implementing Clone for your type. -{% endhint %} +The properties bag is attached to the state adding the field props in the component struct and defining the Properties Type in the component trait implementation. I used to speak about "bag" for a "container" (struct instance in that case) passed around methods. Inside this "container" there is key/values. ... don't mind I will remove it from the doc when I retrieve it.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/yewstack/docs/pull/85#discussion_r422521643, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKFSTPLPOD53QW3LBVFRXTTRQWFO7ANCNFSM4M4JYSSQ.

teymour-aldridge avatar May 09 '20 17:05 teymour-aldridge