-
Notifications
You must be signed in to change notification settings - Fork 5
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
PR to track downstream changes in a fork #12
base: master
Are you sure you want to change the base?
Conversation
[ | ||
line_length: 110, | ||
inputs: ["mix.exs", "{config,lib,test}/**/*.{ex,exs}"] | ||
] |
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.
There should be a final \n at the end of each file.
update deps
delete and log function
value | ||
end} | ||
end) | ||
|> Map.new() |
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.
Pipe chain should start with a raw value.
# this case is entered when the operation type it's a delete operation | ||
{_, regreso} = | ||
Map.from_struct(schema) | ||
|> Map.pop(:__meta__) |
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.
Pipe chain should start with a raw value.
lib/ecto_trail/ecto_trail.ex
Outdated
Map.from_struct(schema) | ||
|> Map.pop(:__meta__) | ||
|
||
IO.inspect(regreso) |
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.
There should be no calls to IO.inspect/1.
value | ||
end} | ||
end) | ||
|> Map.new() |
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.
Pipe chain should start with a raw value.
Hello @AndrewDryga, at Valiot we are actively maintaining and adding features to ecto_trail as we are using it in our core product. If you like we can take over it. You can take a look at our fork here: https://github.com/valiot/ecto_trail/ We've also been thinking in renaming it so we can publish updated versions to hex.pm What do you think? |
Hi @acrogenesis . |
I think it would be nice if we collaborate on improving it instead of maintaining two separate versions. I'm even totally okay to give you write access and rights to publish on Hex, if we agree to not introduce breaking changes (because it's used in our production too). |
Ebert has finished reviewing this Pull Request and has found:
But beware that this branch is 1 commit behind the You can see more details about this review at https://ebertapp.io/github/Nebo15/ecto_trail/pulls/12. |
Maintenance & custom REDACTED fields
…ngesets change data structure for delete changesets
* update deps * add log\4 for handling log only operations * change log * add log_bulk for log a list changes for a list of created structs * fix struct references in log_bulk * change args naming * add log_bulk test for log only behaviour
No description provided.