Lightning Web Components is not an exception.
For this to happen there are a few guidelines that we need to follow. Just because we have embed a child component in parent component, child component is not going to accept the data from parent.
Once after the properties are created we need to decorate the properties in child component using a decorator which is @api.
You can think of @api as public access specifier in Apex.
If we make a property @api the parent component can push data to the child component.
Markup in the Parent component is going to look like this!
However, there are a few limitations
- Once a property in the child component is decorated with @api, no matter what, child component cannot mutate the content of that property.
- If child component wants to update the content of the property, it has to send a request to the parent along with the new value (using events) and parent is going to push the new value to the child component.
if the property in the child component is
taxExemptedBalance then in the parent component the mark-up is going to look like this.
Hope this is useful!