Supporting Legacy Applications #572
justinMBullard
started this conversation in
Ideas
Replies: 1 comment 3 replies
-
|
I'm definitely open to having this flag be added. Maybe call it |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
@TwitchBronBron I will make the name change and then push the branch. |
Beta Was this translation helpful? Give feedback.
-
|
@TwitchBronBron I tried to push my branch but it complained. |
Beta Was this translation helpful? Give feedback.
-
|
You need to make a fork of the repo that you control, push your branch there, and then you can open a PR. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@TwitchBronBron It would be nice to have an option to force BrighterScript compile for .brs files. I have legacy app that I want to leverage BrighterScript functionality, but switching extensions would add a level of unwanted complexity.
I have a branch that add forceBrighterScript to the bsconfig.json file. If you think this would be a good idea, it would be glad to share.
Beta Was this translation helpful? Give feedback.
All reactions