Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • predi predi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kjetil Thuen
  • predipredi
  • Issues
  • #38

Closed
Open
Created Jan 19, 2015 by Kjetil Thuen@kjetilMaintainer

Refactor server code

Having a separate file for Meteor.methods definitions that mostly will just call functions in other files is kind of pointless.

It is also very stupid to make all the functions we need to call live in the global, top-level namespace.

A better approach would be to put the Meteor.method definitions in the apropriate file in the server folder, and stop defining the functions using this.*

This way the actual functions will be "private" and the methods will be exposed through Meteor.methods. Any functions that are called across files (very few) should at least get their own namespace to prevent polluting the root namespace.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking