Bug #8074: variable_* generic methods says we can use ${class_prefix} for a local variable, but this variable doesn't exist - Rudder - Issue Tracker

Actions

Copy link

Bug #8074

closed

variable_* generic methods says we can use ${class_prefix} for a local variable, but this variable doesn't exist

Added by Nicolas CHARLES almost 9 years ago. Updated over 2 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Jonathan CLARKE

Category:

Generic methods

Target version:

ncf-1.2

Pull Request:

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

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

Unfortunately, ${class_prefix} is an empty variable (not filled at all) - so the documentation in each generic method is invalid :(

Actions

Copy link

Updated by Jonathan CLARKE over 8 years ago

Assignee changed from Benoît PECCATTE to François ARMAND

Actions

Copy link

Updated by François ARMAND over 8 years ago

@nicolas: could you please add the following information to let us understand the problem:

- where the doc is ? In the technic editor, or in ncf site ? If the latter, could you add a link ?
- only master is impacted, or 0.x to ?
- what should be the correct documentation ? I'm feeling that you know what it could be, and seing your proposition would help understand what you understood :)

Of course, if you have any other information that can help, don't restrain yourself to the items above.

Thanks!

Actions

Copy link

Updated by François ARMAND over 8 years ago

Assignee changed from François ARMAND to Nicolas CHARLES

Actions

Copy link

Updated by Nicolas CHARLES over 8 years ago

François ARMAND wrote:

@nicolas: could you please add the following information to let us understand the problem:

- where the doc is ? In the technic editor, or in ncf site ? If the latter, could you add a link ?

In the technique editor - in the generic method description

- only master is impacted, or 0.x to ?

Only master - hence the master target

- what should be the correct documentation ? I'm feeling that you know what it could be, and seing your proposition would help understand what you understood :)

We should not mention ${class_prefix} at all, that would be the correct doc