fix for compiling with multiple deps in content config

[mayel]

Solves a compilation error when trying to put this in config:

content: [
  swifti: [
    "lib/**/*swiftui*",
    {:my_custom_lib, "lib/**/*swiftui*"},
    {:other_lib, [
      "lib/**/*swiftui*",
      "priv/**/*swiftui*"
    ]}
  ]
],
output: "priv/static/assets/"

[bcardarella]

Can you add a test for this, we use config/test.exs for this so you just need to add a list to an additional tuple form here: https://github.com/liveview-native/live_view_native_stylesheet/blob/main/config/test.exs#L13

[mayel]

Sure thing, though I'd have to add something like {:another_library, "lib/**/*.*"} to encounter the same issue (since this has to do with compilation order and which deps are already compiled when compiling a module). I tested and tests pass when including that in config after this change FWIW.

[mayel]

I should note that the stylesheet module is also in a dependency itself in our case.

[mayel]

Added the config

[bcardarella]

@mayel can you give me a bit more background in that case, what exactly is failing that requires this change?

[mayel]

Mix.Project.deps_paths only includes already compiled dependencies, so Path.join was trying to join on nil and crashing

[bcardarella]

Oh I see, this is a compilation order issue then. So in that case your PR just ignores the error it doesn't fix the underlying issue of discovering those paths.

[mayel]

Couldn't we just provide a list of patterns, relative to the CWD, instead of specifying otp_aps though?

[bcardarella]

Couldn't we just provide a list of patterns, relative to the CWD, instead of specifying otp_aps though?

In your case you could if you'd like, you can simply just provide a list of relative paths

[bcardarella]

@mayel can you confirm that the relative paths worked for your need? I don't think this needs to be merged if so