Martin Nijboer

Having the same issue: `invalid or unknown type` error is thrown by Ecto for MyUploader.Type. ``` ** (ArgumentError) invalid or unknown type MyApp.ImageUploader.Type for field :image lib/ecto/schema.ex:1727: Ecto.Schema.check_type!/3 lib/ecto/schema.ex:1431: Ecto.Schema.__field__/4...

Version 0.34.0 of the Cloud Storage library has an empty API reference page as well: https://hexdocs.pm/google_api_storage/0.34.0/api-reference.html

Hi @liveforeverx and @jamilabreu, We could open an RFC issue, to gather changes to be made for a version 1 release. Dlex does a lot of things right, is up...

@jamilabreu Yes, I can help. :) @liveforeverx Great! I'm glad the base-API of Dgraph is stable through the different versions. 2: I hadn't seen that, my bad.

When updating, are you casting :uid as a field? I use ``` struct |> cast(params, [ :uid, :title ]) |> validate_required([:uid]) ``` and it works.

To those who are looking for a solution, i.e. to update existing nodes in Dgraph with Ecto changesets: 1. Cast `uid` in your changeset. 2. Validate require `uid` in your...

Thanks for your suggestion. I hadn't planned on introducing this feature 🤔 I'll think on the idea for a bit. The same can be achieved with some business logic, and...

This version addresses https://github.com/martinthenth/goal/issues/64

Hi! Thanks for the report, passing attributes and external values to the macro looks like a useful addition to me. Here is a topic on StackOverflow that describe a similar...

Hey there! I think I have found a working solution to support passing module attributes to the schema. I'll include it in [version 1.0.0](https://github.com/martinthenth/goal/pull/93) 🙂 I did a quick check...