You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not very nice having a large file for apps containing either a large number of components or large chunks of config properties. As a user, I would like to split the definition into multiple files, by component for instance.
However, the current docs don't touch upon this concern, which I think it's a valid one. There should at least be some guidance on this. E.g., by means of using Cue or KCL. For the latter, I've recently come across this post, although the given example is too simple. Besides, I guess using Cue would make more sense because that is the config language chosen by KubeVela and so users should preferably stick to one language for simplicity.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's not very nice having a large file for apps containing either a large number of components or large chunks of config properties. As a user, I would like to split the definition into multiple files, by component for instance.
However, the current docs don't touch upon this concern, which I think it's a valid one. There should at least be some guidance on this. E.g., by means of using Cue or KCL. For the latter, I've recently come across this post, although the given example is too simple. Besides, I guess using Cue would make more sense because that is the config language chosen by KubeVela and so users should preferably stick to one language for simplicity.
Beta Was this translation helpful? Give feedback.
All reactions