configuration.move_type_unsupported

A constant jadpo config move was asked to make a setting has a type one environment variable can't hold, such as a list or an object.

Area 14, Tools; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

A setting is read from one environment variable when the application starts, so its type has to be one a single piece of text decodes as: a text, a number, a date, an enum. A list holds any number of values and an object several fields, and Jadpo won't invent a format to pack them into one variable. So the move is refused and nothing changes.

What it looks like

A library in the accounts domain lists the ways to sign in:

domains/accounts/libraries/security.jadpo:

use accounts/types { LoginAttempts, LoginMethod }library security {    /// Failed sign-ins before an account is locked.    constant max_login_attempts: LoginAttempts = 5    /// The ways to sign in, in the order they are offered.    constant methods: List<LoginMethod> = ["password", "passkey"]}

jadpo config move security.methods

  |7 |     constant methods: List<LoginMethod> = ["password", "passkey"]  |                       ^^^^^^^^^^^^^^^^^ not read from one variable

(agent) at the end of the next: line means your coding agent can make the fix itself.

How to fix it

The question is what a deployment needs to change.

If it only needs to turn a way to sign in on or off, keep the list a constant and add a Bool setting for each one that varies, by hand:

config {    /// Whether people may sign in with a passkey.    passkeys_on: Bool {        default: true    }}

A deployment then sets PASSKEYS_ON=false to offer passwords alone, and the list itself stays in code. If every deployment offers the same ways, the list stays a constant and nothing needs to change.

Related

• Making a constant a setting
• jadpo config move