Forum Discussion

Cole_McDonald's avatar
Cole_McDonald
Icon for Professor rankProfessor
5 hours ago

UIv4 Module Code Editor/IDE funkiness

  1. code reverting (reproducable):  If I make changes to some powershell in the new code editor, then change tabs/windows.  When I change back to the window with my editor, it has reverted to the previous save point.  An Undo will bring back my changes... but it's scary after making a few changes after staring at your code for longer than expected working through logic in your head.
  2. property source error output:  In UIv3, there was side by side output vs. error screens.  We now just get the little info bar at the bottom that states "couldn't do"... but not where/why/what that could be troubleshot.  I'm having to add in a ton of troubleshooting output to the property definition to be able to expose the data I need to fix the scripts.  The one I just completed is nearly 30% error output handling to be able to figure out what is wrong with it.

Other than those two things, I'm pretty happy with the changes from the old.

3 Replies

Sort By
  • Mike_Rodrigues's avatar
    Mike_Rodrigues
    Icon for Product Manager rankProduct Manager
    2 hours ago

    Hi Cole_McDonald​ , thanks for posting this.

    I've sent this post to the LMX team and have asked them to take a look at the code reverting issue. My first guess is it is related to caching, but not sure.

    As for the PropertySource error output, I've got an improvement written up for this but I can't provide a timeline on when it will be done and in product.

    The idea was to basically show standard out and error for both Collection and AD "Test Script". It would be shown in a window or modal, not in some toast message that will disappear in 3 seconds.

    Also, for "Test Active Discovery", I'm hoping to combine this with "Test (AD) Script" so that users can see both their output, and our interpretation of it for help debugging AD issues.

  • Lewis_Beard's avatar
    Lewis_Beard
    Icon for Expert rankExpert
    50 minutes ago

    I can also confirm the first problem. I just developed a datasource to do something, and its frustrating having to remember to comment out the AppliesTo (replacing it with false()) and/or comment out new parts of the code over and over, so that I can hit save, so that I can dare tab out to look at the Swagger API docs or something. :)