Bug 829309 - [CLI] String assignment not possible
[CLI] String assignment not possible
Product: RHQ Project
Classification: Other
Component: CLI (Show other bugs)
Unspecified Unspecified
urgent Severity urgent (vote)
: ---
: RHQ 4.5.0
Assigned To: John Sanda
Mike Foley
Depends On:
Blocks: 824129 826604
  Show dependency treegraph
Reported: 2012-06-06 08:49 EDT by Lukas Krejci
Modified: 2013-09-01 06:10 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-01 06:10:56 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lukas Krejci 2012-06-06 08:49:43 EDT
Description of problem:
In the interactive CLI, the following code breaks:

var a = "whatever";


ReferenceError: "whatever" is not defined. 
var a = whatever ; 

This seems to me like we parsed away the quotes before we submit the line to the javascript interpreter.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. on CLI commandline do:
var a = "whatever";
Actual results:
Error as above

Expected results:
assignment succeeds

Additional info:
This is not limited to assignments - any quoted literal (either single or double quoted) seems to be unqouted before interpreted.

Additionaly, this is NOT present in JON 3.1.0.CR2 (CR3 contains no change in CLI so I'd assume it is not present there either)
Comment 1 John Sanda 2012-06-06 09:41:26 EDT
This is a regression caused by the work I did for bug 826604. I will make this bug a blocker for bug 826604.
Comment 2 John Sanda 2012-06-06 14:34:24 EDT
I pushed a fix to master. The parsing changes only take effect for the script arguments.

commit hash: 5e8863403
Comment 3 Heiko W. Rupp 2013-09-01 06:10:56 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.

Note You need to log in before you can comment on or make changes to this bug.