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.
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
- 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
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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:d6dc604f03a7bfa864d8d7f9b4d9894037e02e36.
Applied in changeset commit:6fa7dcf17c5c30c55dfb108eafdaceb86bdb0425.
- Status changed from Pending release to Released
- Target version changed from 0.x to ncf-0.x
- Priority set to 0
- Project changed from 41 to Rudder
- Category set to Generic methods
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by