Allow loader/dumper be passed through Ecto.embedded_load / Ecto.embedded_dump - #4782
Draft
LostKobrakai wants to merge 1 commit into
Draft
Allow loader/dumper be passed through Ecto.embedded_load / Ecto.embedded_dump#4782LostKobrakai wants to merge 1 commit into
LostKobrakai wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm working on a map based type mirroring
embeds_manyfor transforming back and forth between ecto schema struct data and json.Ecto.ParameterizedTypeseems to support that usecase without much issue.Ecto.embedded_load(OuterSchema, %{…}, :json)works.However the implementation needed to hardcode
:jsonas the format for dumping/loading (just showing one side, but it's a mirror issue for both)Both
Ecto.embedded_load/3as well as the loader passed toc:load/3are&Ecto.Type.embeded_load(&1, &2, format), so it's as far as I can see mostly an issue of being able to compose those things, whereEcto.embedded_load/3doesn't really expect someone to already have the whole dumper callback at hand.https://github.com/elixir-ecto/ecto/blob/master/lib/ecto/type.ex#L431 is where the anonymous function passed to the loader is from.
This PR would be a simple solution here, though not sure if there's sideeffects I'm missing. One benefit to it however is that it's truely scoped to the embedded data usecase and doesn't affect loading from database tables.