The Welkin Suite Forum

apex compile errors don't show line number?



apex compile errors don't show line number?

  • Please log in to reply

#1
windows version welkinsuite

dave

    Posted 01 Apr 2019 and edited 27 May 2019

    I've noticed that code errors in apex don't show reliable line numbers any more.. Usually it says line 1 or 2, regardless of where the actual error is. If I copy/paste that source to the Developer Console, that does show the correct line numbers. 


    This isn't a productive way to do things. Is there a way to get the raw log or some other way to find out where errors are? 



    5 replies to this topic

    #2

    kate.dulko

      Posted 03 Apr 2019

      Hi Dave,


      Thank you for your post.

      We are aware of this issue and we are looking for a way to reproduce this or to some dependencies when exactly this happens, sine on our side this issue is not stably reproduced.

      We would be happy to find a solution to the issue as soon as possible.


      I will keep you updated on our progress on this issue.


      Regards,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      chris

        Posted 08 May 2019 and edited 08 May 2019

        dave, on 01 Apr 2019 - 07:35 PM, said:

        This isn't a productive way to do things. Is there a way to get the raw log or some other way to find out where errors are? 

         Have a look at the "Output" pane (Edit > Output or Ctrl+alt+O) - that's our workaround - however sometimes that message also provides no helpful line no. 


        • 1

        #4

        ihor.zhabolenko

          Posted 10 May 2019

          Hi Chris.

          Thank you for sharing this with us.

          This error that you got in the error panel is what salesforce returns to the IDE when you update your apex class.

          We will work on the improvement of displaying these errors.


          Thanks and have a nice day!



          TWS Team


          #5

          mike.crooks

            Posted 26 May 2019 and edited 26 May 2019

            ihor.zhabolenko, on 10 May 2019 - 07:06 AM, said:

            Hi Chris.

            Thank you for sharing this with us.

            This error that you got in the error panel is what salesforce returns to the IDE when you update your apex class.

            We will work on the improvement of displaying these errors.


            Thanks and have a nice day!


            Hi Ihor,

            I'm getting the same issue since upgrading to TWS Blaze R21.  This used to work in TWS.  In fact, I've seen it work, then stop working a couple of times now between TWS releases.  Unfortunately, I didn't track the release versions where it worked / didn't work otherwise that probably would have helped you pinpoint the issue. It doesn't appear to be a SFDC issue since line numbers are shown using the Developer Console.




            #6

            ihor.zhabolenko

              Posted 27 May 2019

              Hello Mike. 


              Thank you for your response.

              This error that you got in the error panel is what salesforce returns to the IDE when you update your Lightning component.
              I kindly ask you to check what you can see in the Output panel when deploying your changes - there you will find a full error.

              Hope this would help.


              Regards,

              Ihor


              TWS Team





              Boost Your Productivity. Get Started Today

              Try Free Trial