type1fool
An Igniter Saga - Generating Code for Agency Projects
Heyo @zachdaniel!
This topic continues a conversation that started in the Igniter topic.
The component generators turned out nicely, and I can’t wait to use them on new projects.
I’m working on a new generator for adding Commanded and related config to projects.
When I attempt to add config for a module within my app, the generated config is appended to the top-level app config with string atoms as the keys. What I was expecting was a separate block of config with the module as the second argument, followed by the KW list.
Am I doing something wrong, or is this a possible bug?
Expected
config :yolo,
ecto_repos: [Yolo.Repo],
generators: [timestamp_type: :utc_datetime],
consistency: :eventual,
event_stores: [Yolo.EventSystem.EventStore]
config :yolo, Yolo.EventSystem.EventStore,
migration_primary_key: [type: :binary_id],
migration_foreign_key: [type: :binary_id],
migration_timestamps: [type: :utc_datetime_usec]
config :yolo, Yolo.EventSystem.Application,
event_store: [
adapter: Commanded.EventStore.Adapters.EventStore,
event_store: Yolo.EventSystem.EventStore
],
phoenix_pubsub: [adapter: Phoenix.PubSub.PG2, pool_size: 1],
pubsub: :local,
registry: :local,
snapshotting: %{}
Actual
config :yolo,
ecto_repos: [Yolo.Repo],
generators: [timestamp_type: :utc_datetime],
consistency: :eventual,
event_stores: [Yolo.EventSystem.EventStore],
"Elixir.Yolo.EventSystem.EventStore": [
migration_primary_key: [type: :binary_id],
migration_foreign_key: [type: :binary_id],
migration_timestamps: [type: :utc_datetime_usec]
],
"Elixir.Yolo.EventSystem.Application": [
event_store: [
adapter: Commanded.EventStore.Adapters.EventStore,
event_store: Yolo.EventSystem.EventStore
],
phoenix_pubsub: [adapter: Phoenix.PubSub.PG2, pool_size: 1],
pubsub: :local,
registry: :local,
snapshotting: %{}
]
Igniter Code
igniter
|> Igniter.compose_task("cauldron.install.ecto", [])
|> Igniter.Project.Deps.add_dep({:commanded, "~> 1.4"})
|> Igniter.Project.Deps.add_dep({:commanded_ecto_projections, "~> 1.4"})
|> Igniter.Project.Deps.add_dep({:commanded_eventstore_adapter, "~> 1.4"})
|> Igniter.apply_and_fetch_dependencies(yes: true)
|> Igniter.Project.Config.configure("config.exs", app_name, :consistency, :eventual)
|> Igniter.Project.Config.configure("config.exs", app_name, :event_stores, [
event_store_module
])
|> Igniter.Project.Config.configure(
"config.exs",
app_name,
event_store_module,
migration_primary_key: [type: :binary_id],
migration_foreign_key: [type: :binary_id],
migration_timestamps: [type: :utc_datetime_usec]
)
|> Igniter.Project.Config.configure(
"config.exs",
app_name,
event_system_application_module,
event_store: [
adapter: Commanded.EventStore.Adapters.EventStore,
event_store: event_store_module
],
phoenix_pubsub: [
adapter: Phoenix.PubSub.PG2,
pool_size: 1
],
pubsub: :local,
registry: :local,
snapshotting: %{}
)
Module Variables at Runtime
Running the command in the :yolo sandbox app, these are the values used for the config path:
event_store_module = Yolo.EventSystem.EventStore
event_system_application_module = Yolo.EventSystem.Application
Most Liked
zachdaniel
zachdaniel
type1fool
Last Post!
zachdaniel
Yes, that is correct. It’s used with OptionParser, so -m would be used as m: :migration, for example.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #hex









