Results 1 to 2 of 2

Thread: Issue with different placement of custom required classes for dev and prod

  1. #1
    Sencha User
    Join Date
    Feb 2011
    Posts
    111

    Default Issue with different placement of custom required classes for dev and prod

    I have a singleton class called cls.Config. When I am developing I keep this file in ROOT/cls/Config.js and it loads just fine.

    When I build, sencha app build, I need to move this class to ROOT/app/cls/Config.js. How can I make it so I don't need to keep moving files around for builds. Is this a know bug? Should I just write a script that moves files from ROOT/cls to ROOT/app/cls/Config.js, does a build, then moves the files back?

  2. #2
    Sencha Premium User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,451

    Default

    Is the name exactly 'cls.Config'? Do you have the Ext.Loader path setup in app.js and also the app.classpath added in the .sencha/app/sencha.cfg?
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Fullstack Engineer
    ________________
    Modus Create is based on the model of an open source team. We’re a remote, global team of experts in our field. To find out more about the work we do, head over to our website.

    Check out my GitHub:
    https://github.com/mitchellsimoens

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •