Skip to content

[Bug] get_oneline_needs config option is ignored - always forced to True #62

@hliberacki

Description

@hliberacki

The get_oneline_needs option in the [codelinks.projects.<name>.analyse] section of ubproject.toml has no effect. Regardless of the user-specified value, it is always overridden to True inside generate_project_configs().

Location

config.py:879 in generate_project_configs():

def generate_project_configs(
    projects: dict[str, Any],
    conf_dir: Path,
) -> dict[str, ProjectConfig]:
    ...
    for project_name, project_data in projects.items():
        ...
        analyse_config = AnalyseConfig(**analyse_section)
        analyse_config.get_oneline_needs = True  # force to get oneline_need  <-- BUG
        ...

Impact:

All code paths go through this function:

  • CLI (cmd.py → generate_project_configs())
  • Sphinx build (source_tracing.py → generate_project_configs())
  • Config loading (config.py → generate_project_configs())

This means setting get_oneline_needs = false in ubproject.toml is silently ignored everywhere - there is no way for the user to disable oneline need extraction.

Expected behavior:

The user-specified value of get_oneline_needs should be respected. If a user sets get_oneline_needs = false, the analyse step should skip oneline need extraction.

Steps to reproduce:

Set get_oneline_needs = false in ubproject.toml under [codelinks.projects.<name>.analyse]
Run codelinks analyse ubproject.toml
Observe that oneline needs are still extracted despite the config

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