Skip to content
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

Merged
merged 2 commits into from
Jan 6, 2025

Conversation

feloy
Copy link
Contributor

@feloy feloy commented Dec 24, 2024

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?

@feloy feloy requested review from benoitf, jeffmaury and a team as code owners December 24, 2024 12:33
@feloy feloy requested review from cdrage and gastoner December 24, 2024 12:33
@feloy feloy force-pushed the feat-1693/filter-recipes branch from c51c8a0 to 0515c48 Compare December 24, 2024 12:53
Copy link
Contributor

@jeffmaury jeffmaury left a 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 ?

@slemeur
Copy link
Contributor

slemeur commented Jan 2, 2025

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;
Copy link
Contributor

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

@feloy feloy requested review from axel7083 and jeffmaury January 6, 2025 08:40
Copy link
Contributor

@gastoner gastoner left a 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]>
@feloy feloy force-pushed the feat-1693/filter-recipes branch from c5b7e54 to 18a7465 Compare January 6, 2025 09:54
Copy link
Contributor

@axel7083 axel7083 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@feloy feloy merged commit 737780c into containers:main Jan 6, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants