LDT/User Area/New Noteworthy/New Noteworthy 1.1
- 1 New & Noteworthy 1.1
- 1.1 Lighter Documentation
- 1.2 Code analysis
- 1.3 Completion Enhancements
- 1.4 Better Error Handling
- 1.5 Formatter Defaults
- 1.6 Formatter Enhancements
- 1.7 Multi-files Template for Execution Environment
- 1.8 Debugger Introspection Extensibility
- 1.9 Smarter Auto Close
New & Noteworthy 1.1
It is now possible to describe code with significantly less documentation. We analyze the code, filling documentation blanks from it, making documentation more fluent.
Tables are a key concept of Lua. It is mandatory for LDT to handle them right to enable you to code at ease.
We managed to summarize tables nicely in outline. It is obviously now possible to enjoy table content.
- Functions or Methods
- Nested tables
Note: If you click on table fields, you will get code navigation to their definition.
Turn your table into a module is quite simple: simply return it. As below.
Smarter Completion Trigger
Auto-completion is now available after function calls or "object" invocations. It is no longer disturbed by whitespaces.
More Globals Variables Suggested
All globals variables declared in files of your project's buildpath/sourcepath are now suggested in autocompletion.
Note 1: This means LDT could propose you globals variables which may not be available at runtime.
Note 2: This feature could be disabled in the Lua preference page as it could impact autocompletion performance.
Natural Completion On Strings
It now possible to trigger completion on
#string variables without using the
string module. You have completion for
#stringvariable from assignment
#stringvariable from explicit typing
Better Error Handling
To speed up syntax error troubleshooting, the output given is now the Lua 5.1 interpreter one. During the process, syntax error detection became about 10 times faster.
For a better out of the box experience, formatter now uses Lua's 2 spaces indentation standard by default.
The formatter is smarter when formating Lua expressions written on several lines.
Multi-files Template for Execution Environment
When you create your execution environment, it's now possible to include templates made of severals files and folders, in order to help your users to bootstrap their projects. See the create Execution Environment tutorial to get more details.
Note: Existing Execution Environments using the old archive format are still supported.
Debugger Introspection Extensibility
The debugger can now be extended with inspectors to decode custom data. Inspectors allow the debugger to display data in a more human readable way. See the custom debugger introspection tutorial for further details. As explained in the tutorial, the inspector for LuaJIT's cdata is shipped with LDT.
Smarter Auto Close
Auto close got smarter and feels more natural. It is a silent improvement. If you did not notice it, it means it works just fine.