![]() ![]() ![]() If this wasn't the case, modifying a component could break other components! This prevents separate components from even accidentally having implicit dependencies on each other.Likewise, child components will not receive the data selected by their parents (again, unless the child selected those same fields). This means that the parent component will not receive the data selected by a child component (unless that parent explicitly selected the same fields).the fragment reference, doesn't actually contain any of the data declared by the child UsernameSection component instead, UsernameSection will use the fragment reference to read the data it declared internally, using useFragment. Note that in this case the user passed to UsernameSection, i.e.In other words, a fragment reference is like a pointer to a specific instance of a type that we want to read data from. As we've mentioned before, a fragment reference is an object that Relay uses to read the data declared in the fragment definition as you can see, the child UsernameSection_user fragment itself just declares fields on the User type, but we need to know which specific user to read those fields from this is what the fragment reference corresponds to. UsernameSection expects a fragment reference as the user prop.UserComponent both renders UsernameSection, and includes the fragment declared by UsernameSection inside its own graphql fragment declaration. ![]() If you need to render data from multiple fragments inside the same component, you can use useFragment multiple times: This makes it easy to identify which fragments are defined in which modules and avoids name collisions when multiple fragments are defined in the same module. In order to easily achieve this, we name fragments using the following convention based on the module name followed by an identifier: _.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |