Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Domino Designer
Categories LotusScript
Created by Guest
Created on Nov 15, 2024

Stop reordering contents of raw .lss file after saving in Designer

Our project team utilizes Git version control to keep our incremental code changes well-organized. Because Git closely looks at file modification differences, however, our team constantly has to place significant time and effort into counteracting Designer's massively-redundant re-ordering of LotusScript (.lss) file contents. Even if you make a one-line code change to a subroutine inside of a lss library module, Designer -- for some unknown, unjustified, or otherwise completely illogical reasoning -- completely re-orders the contents of the raw lss file such that the order in which all specified subroutines/functions appear in the raw .lss file completely changes.

Again, because Git closely looks at file modification differences (as it should), this consistently creates scenarios where one-line code changes/additions/deletions become 100's if not 1000's of file content differences per line inside the raw .lss file. The process of determining and then commiting (via `git commit` command) what actual code changes occurred becomes a diabolically tedious, infuriating, and cumbersome process all because of an arbitrary re-ordering imposed by Designer that is completely unnecessary.

This "feature" needs to be removed as this behavior serves no meaningful purpose nor benefits to developers that actively use Designer.

  • Attach files