Skip to content

archlens init should generate a usable config #100

@mircealungu

Description

@mircealungu

Problem

Running `archlens init` from a project directory generates a config with empty `rootFolder` and `name`, which immediately fails schema validation when you run `archlens render`.

Current template:
```json
{
"name": "",
"rootFolder": "",
"fileExtensions": [".cs"]
}
```

The `name` field is populated with `os.path.basename(os.getcwd())`, but `rootFolder` is left empty, violating the schema's `minLength: 1` constraint.

Expected behavior

`archlens init` followed by `archlens render` should just work with sensible defaults:

  • `rootFolder` should default to `"."` (current directory)
  • `fileExtensions` should be auto-detected by scanning for source files in the directory
  • Or at minimum, the template should have `rootFolder: "."` so it passes validation

Steps to reproduce

```bash
cd some-csharp-project
archlens init
archlens render # fails with ValidationError: '' should be non-empty
```

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions