-
Notifications
You must be signed in to change notification settings - Fork 1
fix challenge update #10
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
Conversation
@@ -31,6 +31,7 @@ const protoConfig = [ | |||
`--descriptor_set_out ${PROTO_REFLECTIONS}`, | |||
`--proto_path ${PROTO_DIR} ${PROTO_DIR}/common/*.proto`, | |||
`--proto_path ${PROTO_DIR} ${PROTO_DIR}/domain-layer/challenge/*.proto`, | |||
`--proto_path ${PROTO_DIR} ${PROTO_DIR}/domain-layer/legacy/*.proto`, |
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.
Why do we need legacy here? This doesn't seem right. domain-challenge should not be building legacy models - that's a function of ACL
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 were using a legacy model which was throwing an import error
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.
Can we point to it please - I'll take a look. But we should be importing legacy stuff here - if we did it's a mistake Any imports must come through domain-acl.
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.
Please see my comments.
No description provided.