As I understand it, the compiler should just take care of differences
between JS and SWF, as long as your targets option is correct. VSCode
shouldn't need to do anything special except to pass in the correct
options.
There's nothing related to dual changes on my to-do list at this time, but
maybe I missed something important...
- Josh
On May 31, 2017 7:52 PM, "Harbs" <harbs.li...@gmail.com> wrote:
Josh,
VS Code is now reporting lots of errors in the Problems window. I’m
guessing it does not know how to differentiate between JS and SWF builds
using dual?
Is that something on your to-do list?
Thanks,
Harbs
> On Jun 1, 2017, at 5:10 AM, Harbs <harbs.li...@gmail.com> wrote:
>
> Bingo. Thanks!
>
> SWF output still gets all kinds of errors, but the JS output is pretty
error free. I still have some fixing up to do before I can see how well it
actually works, but at least the compiler is not complaining now.
>
>> On Jun 1, 2017, at 4:45 AM, Josh Tynjala <joshtynj...@gmail.com> wrote:
>>
>> Try replacing the js-output-type compiler option with:
>>
>> "targets": ["JSFlex"]
>>
>> - Josh
>>
>> On May 31, 2017 6:26 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>>
>>> I’m using asconfig in VSCode to compile with these settings:
>>> "config": "flex",
>>> "compilerOptions": {
>>> "debug": false,
>>> "js-output-type": "flexjs",
>>> "source-map": false,
>>> "library-path": [
>>> "lib"
>>> ],
>>>
>>>> On Jun 1, 2017, at 1:04 AM, Justin Mclean <jus...@classsoftware.com>
>>> wrote:
>>>>
>>>> HI,
>>>>
>>>>> Am I missing something?
>>>>
>>>> Perhaps try <targets>JSFlex</targets> in your pom.xml? I believe the
>>> name changed from pre to post dual branch.
>>>>
>>>> Justin
>>>>
>>>
>>>
>
