Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-14185

Code Analyzer: Alloy: Warning or Error found for an Alloy project refer to the Resources project files, instead of App folder


    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Invalid
    • Affects Version/s: Release 3.1.1
    • Fix Version/s: None
    • Component/s: Code Processor
    • Labels:
    • Environment:

      TiSDK 3.1.1.v20130611104924
      Appcelerator Studio
      Titanium Code Processor 1.0.1-cr4
      Alloy 1.1.3-cr


      Problem description

      When a Warning or Error is found by the Code Analyzer for an Alloy project, Warning or Error icons are placed in the code gutter in the Resources file projects instead than in the App file projects. The result is that the Project is now marked with the red/white error icon and the 'Errors in Workspace' alert is displayed every time the project is being build.

      'Resources' folder is by default not visible for Alloy projects on Studio, so the default result is also that the project is marked with an error icon, but the user can't see any other red error icon next to any visible Project file.

      Also, having an error or a warning reported for the Alloy compiled code in the Resources folder does not add value for the user as the intended behavior is not to manually modify the compiled code files in the Resources (user should only handle Alloy files, all included into the App folder).

      Steps to reproduce

      Paste the sample code. Note the code error in the controller.js , where foobar is actually not a function.
      The error is correctly reported by the Code Analyzer (see the screenshot), also getting the correct position in the Alloy project.
      However, in Studio the Error icon is placed in 'Resources/alloy/controllers/index.js' , which is hidden by default and should in any case manually modified by the user.


      	backgroundColor : 'blue'


      	<Window title="Win 1" id='mainwin'>
      		<Label>I am Window 1</Label>


      Since code processor have knowledge about the original source code and the generated source code, it is more viable for the code processor to covert the filename/filepath referenced in errors or warnings to the original code instead of referencing to generated source code.


      Alloy projects could also be displaying errors or warning relative to compiled code, generated by Alloy, not necessarily linked to "App" alloy files created by the user but only present in "Resources" folder.


          Issue Links



              • Assignee:
                bhughes Bryan Hughes
                fcasali Federico Casali
              • Watchers:
                1 Start watching this issue


                • Created:

                  Backbone Issue Sync

                  • Titanium SDK/CLI <> Titanium Mobile
                    Synced with:
                    Sync status:
                    Last received:
                    Last sent:

                    Git Integration