vs what your code do:
:oop → "oop" → "Oop" → Elixir.Oop
Something in your code tries to reference this long module where it should Oop or you should do other concatenation (not with Elixir, but for example a parent module i.e. __MODULE__). Since I have shared small example I have concatenated said module with Example module.
Ahh, Thank you yes you are right
defmacro sub_field(name, _type, opts \\ [], do: block) do
ast = register_struct(block, opts)
name =
name
|> Atom.to_string()
|> Macro.camelize()
|> String.to_atom()
%Macro.Env{module: mod} = __CALLER__
module_name = Module.concat(mod, name)
quote do
defmodule unquote(module_name) do
unquote(ast)
end
end
end
but I think it just supports one level nested, because I use __CALLER__
I think it does not support
defmodule TestNestedStruct do
use GuardedStruct
guardedstruct do
field(:title, String.t())
field(:subject, String.t())
sub_field(:oop, String.t(), enforce: true) do
field(:title, String.t())
field(:fam, String.t())
sub_field(:sop, String.t(), enforce: true) do
field(:title, String.t())
end
end
field(:site, String.t())
end
end
so I wont be able to fix it I create another post for it. thank you
__CALLER__ looks good for me and there should not be any problem. As always just an example to check what you worry about:
defmodule MyLib do
defmacro my_macro(name, do: block) do
module =
name
|> Atom.to_string()
|> Macro.camelize()
|> String.to_atom()
|> then(&Module.concat(__CALLER__.module, &1))
quote do
defmodule unquote(module) do
_ = unquote(block)
end
end
end
end
defmodule A do
import MyLib
my_macro :b do
my_macro :c do
IO.inspect(__MODULE__)
end
end
end
The above code prints A.B.C. 
Hi again 
, I have a question, when I move my module and macro inside a test, it does not work, I think inside test it takes a time to compile and the functions are called faster than the macro
test "nested macro field" do
defmodule TestNestedStruct do
use GuardedStruct
guardedstruct do
field(:title, String.t())
field(:subject, String.t())
sub_field(:oop, String.t(), enforce: true) do
field(:title, String.t())
field(:fam, String.t())
sub_field(:soos, String.t(), enforce: true) do
field(:fam, String.t())
end
end
field(:site, String.t())
end
end
IO.inspect(TestNestedStruct.__struct__())
IO.inspect(TestNestedStruct.Oop.__struct__())
IO.inspect(TestNestedStruct.Oop.__info__(:functions))
IO.inspect(TestNestedStruct.Oop.Soos.__struct__())
IO.inspect(TestNestedStruct.Oop.Soos.__info__(:functions))
IO.inspect(TestNestedStruct.keys())
assert %TestNestedStruct.Oop{
fam: nil,
title: nil
} = TestNestedStruct.Oop.__struct__()
end
The error:
error: MishkaDeveloperToolsTest.GuardedStructTest.TestNestedStruct.Oop.__struct__/0 is undefined, cannot expand struct MishkaDeveloperToolsTest.GuardedStructTest.TestNestedStruct.Oop. Make sure the struct name is correct. If the struct name exists and is correct but it still cannot be found, you likely have cyclic module usage in your code
test/guarded_struct_test.exs:542: MishkaDeveloperToolsTest.GuardedStructTest."test nested macro field"/1
defmodule TestNestedStruct do
use GuardedStruct
guardedstruct do
field(:title, String.t())
field(:subject, String.t())
sub_field(:oop, String.t(), enforce: true) do
field(:title, String.t())
field(:fam, String.t())
sub_field(:soos, String.t(), enforce: true) do
field(:fam, String.t())
end
end
field(:site, String.t())
end
end
test "nested macro field" do
IO.inspect(TestNestedStruct.__struct__())
IO.inspect(TestNestedStruct.Oop.__struct__())
IO.inspect(TestNestedStruct.Oop.__info__(:functions))
IO.inspect(TestNestedStruct.Oop.Soos.__struct__())
IO.inspect(TestNestedStruct.Oop.Soos.__info__(:functions))
IO.inspect(TestNestedStruct.keys())
assert %TestNestedStruct.Oop{
fam: nil,
title: nil
} = TestNestedStruct.Oop.__struct__()
end
__struct__ inside a variable, it print the output but it shows me this warning....warning: MishkaDeveloperToolsTest.GuardedStructTest.TestNestedStruct.Oop.__struct__/0 is undefined (module MishkaDeveloperToolsTest.GuardedStructTest.TestNestedStruct.Oop is not available or is yet to be defined)
test/guarded_struct_test.exs:541: MishkaDeveloperToolsTest.GuardedStructTest."test nested macro field"/1
It’s not a part of public API and therefore no answer guarantees you a working solution using it. Why cant you use %module{…} notation?
First of all why you do this? Much more common is to place it in test/fixtures/my_fixture.ex file …
There was some talk about this issue … I think it was about Elixir scripts i.e. exs files called like elixir my_script.exs. There was a question I think about ecto’s macros not working on same level where module is defined, but working inside some function … Somebody from Elixir’s core team (most probably José Valim) commented it and that it’s known limitation.