-
Notifications
You must be signed in to change notification settings - Fork 5
Add require_model to the brick list #93
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
base: main
Are you sure you want to change the base?
Conversation
68e4ca0 to
a091a26
Compare
lucarin91
left a comment
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.
You should regenerate the openapi
mirkoCrobu
left a comment
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.
You should regenerate the openapi
And after regenerating it, you can integrate "internal/e2e/daemon/brick_test.go"(test: func TestBricksList(t *testing.T) ), checking the new field.
| require.Equal(t, "Image Classification", b.Name) | ||
| require.Equal(t, "mobilenet-image-classification", b.ModelName) | ||
| require.True(t, b.RequireModel) | ||
| require.True(t, b.ModelRequired) |
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.
I would add two additional unit tests: "require_model: false" and a missing "require_model" in the yaml
Motivation
This PR add the required_model field on brick:
Additional Notes
require_modelboolen in brick list/details #88require_modelfor the app bricks (installed into an app) #90