Bug 1041974 - [RFE][horizon]: Automate style checking for javascript files
Summary: [RFE][horizon]: Automate style checking for javascript files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M2
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact: Ido Ovadia
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_icehouse-2 upstrea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:23 UTC by RHOS Integration
Modified: 2014-09-08 05:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-08 15:43:12 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0855 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Dashboard 2014-07-08 19:33:24 UTC

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


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