Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • RAPID-MIX_API RAPID-MIX_API
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • rapid-mix
  • RAPID-MIX_APIRAPID-MIX_API
  • Issues
  • #29

Closed
Open
Created Sep 20, 2017 by Francisco Bernardo@franciscoOwner

Dealing with boilerplate code

Examples in codeCircle have too much boilerplate code, which users considered noisy, difficult to read and to navigate. JSFiddle deals with it using a leaner approach which separates HTML and JS.

Recommendation: In the case of CodeCircle, which doesn't separate code, it means isolating functionalities in code sections clearly delimitating them with large comment blocks (e.g., "data acquisition" block, "setting up ML" block, "UI event handling" block, "UI logic" block, "data storage and retrieval" block, etc.)

Assignee
Assign to
Time tracking