-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add optional language and frameworks fields to recipes #2297
Conversation
Signed-off-by: Philippe Martin <[email protected]>
c51c8a0
to
0515c48
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As those fields are optional, I think we should keep the existing recipe catalog version to favor backward compatibility
Wondering if language should not be multi valued @slemeur WDYT ?
Yeah, I agree that the language could have multiple values. It's highly possible that a recipe might bridge different tools and possibly multiple microservices written with different languages. |
@@ -57,4 +57,6 @@ export interface Recipe { | |||
* server the recipe requires | |||
*/ | |||
backend?: string; | |||
language?: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A recipe might be backend / frontend so rust in backend and js in frontend, might be a good idea to have it as an array
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codewise LGTM
Signed-off-by: Philippe Martin <[email protected]>
c5b7e54
to
18a7465
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Philippe Martin [email protected]
What does this PR do?
Add optional language and frameworks fields to recipes.
I don't know if we want to increase the catalog version number when adding optional fields. @axel7083 @jeffmaury WDYT?
Screenshot / video of UI
What issues does this PR fix or reference?
Related to #1693
How to test this PR?