component1, and to component2 as an API
variable. The reason is that we must get modification on
"theEditedArtist" made in component2 back to Main. Identically,
Boolean API variables are passed to component1 from Main to enable/
disable blocks visibility in component1. Other Bo
o it... The aim of the
application is to offer an interface to manage contents stocked in a
database. I have at the end many reusable web components with many api
variables. Within these api variables I send the edited objects and a
lot of booleans to deal with the layout with conditionals. Is it a
c
ts stocked in a
database. I have at the end many reusable web components with many api
variables. Within these api variables I send the edited objects and a
lot of booleans to deal with the layout with conditionals. Is it a
common way to do things in a web objects application ? Doesn't it look
l
s with many api
variables. Within these api variables I send the edited objects and a
lot of booleans to deal with the layout with conditionals. Is it a
common way to do things in a web objects application ? Doesn't it look
like dirty javascript ?
What are the differences between api variables
