-
Notifications
You must be signed in to change notification settings - Fork 40
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
Support diffing blueprints via Diffus #7261
Conversation
This is the second step in #7240. The next steps will use this support to replace our handrolled code for generating diffs and generate output from the diffus based diffs.
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.
Easy enough! This seems a lot nicer than maintaining hand-roll diffs, to put it mildly.
@@ -187,6 +190,7 @@ pub struct Blueprint { | |||
pub clickhouse_cluster_config: Option<ClickhouseClusterConfig>, | |||
|
|||
/// when this blueprint was generated (for debugging) | |||
#[diffus(ignore)] |
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.
Do we also want to ignore creator
and comment
? I think we don't care about those in diffs either.
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.
After discussion with Rain, I'm going to write a visitor. I think it's worth allowing the possibility to diff these via visitor implementations.
This is wonderful -- thanks again for all the work and the demo today @andrewjstone! |
This is the second step in #7240.
The next steps will use this support to replace our handrolled code for generating diffs and generate output from the diffus based diffs.