Story #4128

[Workbench] [refactor] JavaScript refactoring

Added by Tim Pierce about 6 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Arvados Future Sprints
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Some JavaScript maintenance we need in Workbench:

  • As much code as possible should be refactored out of views into their own assets.
  • Do not embed Ruby code in JavaScript. Ruby values should be passed only into variable assignments and function arguments, to minimize the risk of injection attacks.
  • Refactor JS code with an eye toward making unit testing possible.

History

#1 Updated by Tim Pierce about 6 years ago

  • Tracker changed from Bug to Story
  • Description updated (diff)
  • Category set to Workbench

#2 Updated by Tom Clegg over 3 years ago

  • Subject changed from [Workbench] JavaScript refactoring to [Workbench] [refactor] JavaScript refactoring

Also available in: Atom PDF