Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

--params argument does not work in v0.12.0 #213

Closed
teerapap opened this issue Nov 1, 2013 · 1 comment
Closed

--params argument does not work in v0.12.0 #213

teerapap opened this issue Nov 1, 2013 · 1 comment

Comments

@teerapap
Copy link

teerapap commented Nov 1, 2013

In version 0.12, --params passed via command-line does not work. It does not get converted to a proper object.

From #32, I try protractor someConfig.js --params number=1
and then browser.params is

{ '0': 'n',
  '1': 'u',
  '2': 'm',
  '3': 'b',
  '4': 'e',
  '5': 'r',
  '6': '=',
  '7': '1' }
@teerapap
Copy link
Author

teerapap commented Nov 1, 2013

Oh! my mistake. It needs to be --params.number=1. Now it works.

I see the right way in 02cb819 commit message

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant