Bug 1041974

Summary:	[RFE][horizon]: Automate style checking for javascript files
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aberezin, aortega, dnavale, jpichon, markmc, mrunge, yeylon
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/js-coding-style-checks
Whiteboard:	upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-08 15:43:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 20:23:01 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/js-coding-style-checks.

Description:

Horizon currently doesn't have any coding standards for javascript files. We need to have an agreement over one and then automate style checking for js, just like pep8 does for python. It also involves fixing all the inconsistencies in the existing codebase and making changes according to the accepted coding standards.

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-23 20:51:12 UTC

Moving to POST based on upstream status (Implemented).

Comment 3 Ido Ovadia 2014-03-23 15:07:23 UTC

Does it need QE verificaton?
If yes, please provide any steps

Comment 4 Matthias Runge 2014-03-25 14:10:44 UTC

This can not be tested by QE. It's intended to support developers.

Comment 5 Ido Ovadia 2014-04-13 13:02:21 UTC

Regression passed

Comment 7 errata-xmlrpc 2014-07-08 15:43:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0855.html