-
Notifications
You must be signed in to change notification settings - Fork 47
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
[Proposal] Add Namespace Source Literals #1354
[Proposal] Add Namespace Source Literals #1354
Conversation
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.
looks good to me! Nice work.
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.
Actually, on second thought, I wanted to have a quick discussion about the variable names. Would appreciate your thoughts.
@addison-adler can you fix the failing unit test? |
Head branch was pushed to by a user without write access
Test failure caused by a casing mismatch; re-testing now |
already on it and fixed! 😁 |
Oh, it doesn't like variables that use snakecase.. okay lemme make those hash keys into strings again 😅 |
Head branch was pushed to by a user without write access
@TwitchBronBron all good now! |
I'd like to add two source literals:
SOURCE_NAMESPACE
andSOURCE_NAMESPACE_ROOT
SOURCE_FUNCTION_NAME
literalPKG_PATH
, but that changes every file, whereas a namespace can span multiple filesLive Transpile Preview (pulled from VSCode)
Brighterscript:
Transpiled
Example Use Case
for debugging & log filtering