Bug #5558: When we use variables in parameters, for a generic methods that have a condition, the resulting generated not applicable file is invalid - Rudder - Issue Tracker

Actions

Copy link

Bug #5558

closed

When we use variables in parameters, for a generic methods that have a condition, the resulting generated not applicable file is invalid

Added by Nicolas CHARLES about 10 years ago. Updated over 2 years ago.

Status:

Released

Priority:

N/A

Assignee:

Jonathan CLARKE

Category:

Generic methods

Target version:

ncf-0.x

Pull Request:

https://github.com/Normation/ncf/pull...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

If I want to use a generic methods, with condition linux, on file name ${env.filename}, then the generated files for report na will use _env_filename as class prefix, which is plain wrong

Subtasks 1 (0 open — 1 closed)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nicolas CHARLES about 10 years ago

Status changed from New to Pending technical review
Assignee set to Jonathan CLARKE
Pull Request set to https://github.com/Normation/ncf/pull/124/files

https://github.com/Normation/ncf/pull/124/files

Actions

Copy link

Updated by Nicolas CHARLES about 10 years ago

Ha, the logger_rudder should also canonify the class passes in parameter, as class_noop, for the case when we have ${} in them; they are not canonified automagically

Actions

Copy link