-
Notifications
You must be signed in to change notification settings - Fork 55
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
Diff mappings #45
Comments
Thanks for the question! I admit, this feature might not be the most useful, so I don't think it's worth spending a lot of time on. The idea would be if you had several time series indices on a cluster to be able to compare |
I've got a POC going with https://github.com/nsf/jsondiff The problem is that the output is absolutely massive because of the mapping file sizes. I was working on a custom reporter for https://github.com/google/go-cmp but it was a bit over my head. The default settings for go-cmp is very verbose, so we would need a custom reporter, as seen here: https://pkg.go.dev/github.com/google/go-cmp/cmp@v0.5.0?tab=doc#example-Reporter. The example reporter only outputs the actual diff with the path leading up to that, but it's still very dense so would need some customisation.
I also have some reflect value issues here. |
The main issue for go-cmp is that we don't have a struct this can be marshalled in to, so everything is a |
It looks like nsf/jsondiff#6 was finally solved! Going to give it a try |
I saw in the functionality
diff mappings
in the roadmap.Have you already given any thought on how should this be implemented ? (calling git from the go code?)
The desired behaviour of this functionality using the CLI, I guess would be to print the diff git style on the console, but how should this functionality behave when vulcanizer is used as a library ?
The text was updated successfully, but these errors were encountered: