Open Mahmoud-Emad opened 2 months ago
We can keep these separated variables but make use of (for example) v-model:ipv4
this will pass ipv4
& onUpdate:ipv4
which can be checked in $attrs
prop in any vue component
ipv4
at all so we remove that fieldipv4
without onUpdate:ipv4
so we mark that switch as readonlyipv4
and onUpdate:ipv4
so we make that input interactive with user clicks
Which package/s are you suggesting this feature for?
No response
Is your feature request related to a problem? Please describe
N/A
Describe the solution you'd like
In the current implementation, the network configurations (e.g., IPv4, IPv6, Mycelium, Planetary, WireGuard) are managed individually within each parent component. This approach involves defining constants as references in the parent component and binding these values to the child
Networks
component. Here’s an example:So, imagine, if we want to enable only the
mycelium
to all of the solutions/applications, we need to go around all components change the value of all networks then enable only themycelium
network, so hard? No?My proposal is to modify the
Networks
component and let it expose the values, e.g. defining a store to store the actual values of the networks, also setting the initial value in this store will reflect to all of the solutionsDefine network settings as reactive properties in this store.
Update the Networks Component:
Bind the Centralized Configuration to Components:
Access and Use the Configuration in VM Deployment: