Alex A.

@dietergeerts thanks for the idea! I am leaning towards having `no-browser` as a separate new rule turned off by default for 3 main reasons: - backwards compatibility - to keep...

@dietergeerts yes, please. Let me know if you have any questions or need help.

@jlin412 good idea. I was afraid I should not be sticking to jasmine/mocha framework style in the plugin that much. Do you think it would be better to generalize `no-describe-selectors`...

@igniteram would really appreciate it. Let me know if you need any help or any adjustments to the current rules or exposed settings to support the new cucumber rules. Thank...

@igniteram by the way, you can ping me on [gitter](https://gitter.im/alecxe/eslint-plugin-protractor) whenever needed

@jlin412 gotcha, please disable the rules that don't apply to your particular case.

Note to self: this rule implementation should trigger the major version bump. The plugin version 2 which would have the support for separate config/spec/pageobject specific rules.

Thanks! Do you think it makes sense to make the number of `expect()` per `it()` configurable, or just force it to no more than 1?

Interesting idea to check the first word to be a verb. But, I think letting users to have a specific pattern configured would be more flexible overall. Thanks.

@DianaSuvorova in our jasmine/protractor codebase, I would probably just enforce `^should`. Well, ideally I mean "should \", but it would be difficult to automate "do something" without natural language processing,...