-
Notifications
You must be signed in to change notification settings - Fork 69
SLua editor: multi-line strings and comments #3807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
along with missing meshoptimizer license
@@ -104,47 +104,42 @@ | |||
<key>boolean</key> | |||
<map> | |||
<key>tooltip</key> | |||
<string>Lua boolean: represents a true or false value.</string> | |||
<string>Boolean: represents a true or false value.</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should lua tooltips really be in app_settings? We need them to be localizable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a default LSL keywords file in the same location, so this is correct.
For LSL, we also receive one from the server, but that isn't supported for SLua yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default keyword for LSL updates from server, I'm not sure it's something that should be replicated for Lua.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's planned to be implemented later. For now we just use a placeholder class LLSyntaxLua.
No description provided.