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

followup PR to address comments for dynamic datasource providers #863

Merged

Conversation

mavilein
Copy link
Contributor

@mavilein mavilein commented Jun 30, 2020

followup for this PR to address comments.

@mavilein mavilein changed the title add masking for datasource URLs [WIP] followup PR to address comments for dynamic datasource providers Jun 30, 2020
Copy link
Contributor

@yoshuawuyts yoshuawuyts left a comment

Choose a reason for hiding this comment

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

💯

Comment on lines 14 to 16
#[serde(rename_all = "camelCase")]
#[derive(Clone, Debug, Serialize)]
pub struct StringFromEnvVar {
Copy link
Contributor

@yoshuawuyts yoshuawuyts Jun 30, 2020

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.

Copy link
Contributor Author

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?

Copy link
Contributor

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 (:

@mavilein mavilein added this to the 2.2.0 milestone Jun 30, 2020
@mavilein mavilein changed the title [WIP] followup PR to address comments for dynamic datasource providers followup PR to address comments for dynamic datasource providers Jun 30, 2020
@mavilein mavilein merged commit c29fbcd into master Jun 30, 2020
@mavilein mavilein deleted the datamodel-parser/followup-feedback-dynamic-providers-pr branch June 30, 2020 15:12
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.

2 participants