-
Notifications
You must be signed in to change notification settings - Fork 245
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
followup PR to address comments for dynamic datasource providers #863
followup PR to address comments for dynamic datasource providers #863
Conversation
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.
💯
#[serde(rename_all = "camelCase")] | ||
#[derive(Clone, Debug, Serialize)] | ||
pub struct StringFromEnvVar { |
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.
Taking a closer look at #800 (comment), it's still unclear to me how this construct works. When is from_env_var
populated? When is value
populated? There seems to be some intent behind how to construct and use this struct, and it's unclear to me what that is.
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.
Does the line below not clarify that?
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.
On re-reading it I guess it's fine, though I was hoping it could be clearer. We now have a struct member communicating intent over the whole struct which is something I would expect to live at the top level of the struct declaration site.
But I feel like we've talked quite a bit about this patch already; feel free to merge this PR as-is (:
followup for this PR to address comments.