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
Thanks for building this - I expect it will be very useful.
What do you think about having the linter warn if folks aren't following "best practices"? These aren't things that would break a Configuration or Composition, but they are things that make them more readable, and in some cases "future proof" them.
The two examples that immediately come to mind are:
Warn if any entries in the resources array are missing a name field. When this is the case Composition operates in a kind of "legacy mode". It can't support deleting or reordering entries in the resources array, and can't support Composition Functions.
Warn if any type field is missing. This is mostly a readability thing - we introduced a couple of type fields as optional when they probably should have been required. I think writing the type out each time makes it more obvious what the Composition is doing.
The text was updated successfully, but these errors were encountered:
Thanks for building this - I expect it will be very useful.
What do you think about having the linter warn if folks aren't following "best practices"? These aren't things that would break a Configuration or Composition, but they are things that make them more readable, and in some cases "future proof" them.
The two examples that immediately come to mind are:
resources
array are missing aname
field. When this is the case Composition operates in a kind of "legacy mode". It can't support deleting or reordering entries in theresources
array, and can't support Composition Functions.type
field is missing. This is mostly a readability thing - we introduced a couple oftype
fields as optional when they probably should have been required. I think writing the type out each time makes it more obvious what the Composition is doing.The text was updated successfully, but these errors were encountered: