type1fool

type1fool

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. :tada: 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

First 6 of 6 Posts Switch mode

type1fool

type1fool OP

After generating a new config block with module names rendered as proper atoms, this does appear to be a bug. I opened #104 in the repo for this.

zachdaniel

zachdaniel

Creator of Ash

:bowing_man: thanks! I’ll take a look :slight_smile:

zachdaniel

zachdaniel

Creator of Ash

Fixed :smiley:

type1fool

type1fool OP

Excellent! :fire::fire::fire: I will give it a shot tomorrow.

type1fool

type1fool OP

@zachdaniel Congrats on releasing the update feature!

I’m rewriting a Mix.Task with Igniter, and I’m curious what Igniter.Mix.Task.Info.aliases would do and how to use it. I’m guessing this is where short options would go a la --migration-m. Is that right?

Do you have an example?

zachdaniel

zachdaniel

Creator of Ash

Yes, that is correct. It’s used with OptionParser, so -m would be used as m: :migration, for example.

— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New

We're in Beta

About us Mission Statement