Compiler warnings !

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Compiler warnings !

serkan
Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

                         visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan
Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

Carlos Rovira-2
Hi,

it would be good to have some @ comment to disable per case, but currently you can only turn all on/off:





El lun., 8 jun. 2020 a las 16:44, serkan (<[hidden email]>) escribió:
Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

                         visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan


--
Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

serkan
Thanks Carlos,

Serkan

8.06.2020 17:49 tarihinde Carlos Rovira yazdı:
Hi,

it would be good to have some @ comment to disable per case, but currently you can only turn all on/off:





El lun., 8 jun. 2020 a las 16:44, serkan (<[hidden email]>) escribió:
Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

                         visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan


--

Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

Alex Harui-2
In reply to this post by serkan

There are two ways, depending on the scenario:

 

  1. Make sure none of the properties in the binding expression are of type Object and that the instances support change events
  2. Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 

From: serkan <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Monday, June 8, 2020 at 7:44 AM
To: "[hidden email]" <[hidden email]>
Subject: Compiler warnings !

 

Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

                         visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan

Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

serkan
Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

  1. Make sure none of the properties in the binding expression are of type Object and that the instances support change events
  2. Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 

From: serkan [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Monday, June 8, 2020 at 7:44 AM
To: [hidden email] [hidden email]
Subject: Compiler warnings !

 

Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

                         visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan


Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

Alex Harui-2

I don’t know.  Try “as XML” and see if that solves the problem.

 

From: serkan <[hidden email]>
Date: Monday, June 8, 2020 at 1:26 PM
To: "[hidden email]" <[hidden email]>, Alex Harui <[hidden email]>
Subject: Re: Compiler warnings !

 

Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

1)      Make sure none of the properties in the binding expression are of type Object and that the instances support change events

2)      Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 

From: serkan [hidden email]
Reply-To: [hidden email] [hidden email]
Date: Monday, June 8, 2020 at 7:44 AM
To: [hidden email] [hidden email]
Subject: Compiler warnings !

 

Hi,

Is it possble to get rid of these warnings ?

Warning: Data binding will not be able to detect assignments to 'isResumable'.

                         visible="{data.visualParams.commandabilityParams.isResumable == true}"

Thanks,
Serkan




Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

serkan
Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know.  Try “as XML” and see if that solves the problem.

 

From: serkan [hidden email]
Date: Monday, June 8, 2020 at 1:26 PM
To: [hidden email] [hidden email], Alex Harui [hidden email]
Subject: Re: Compiler warnings !

 

Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

1)      Make sure none of the properties in the binding expression are of type Object and that the instances support change events

2)      Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 






Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

Alex Harui-2

Up to you.  I will try to find some time to see why “as XML” did not work.  The risk of suppressing a warning is that you might miss an important one.

 

-Alex

 

From: serkan <[hidden email]>
Date: Tuesday, June 9, 2020 at 2:01 PM
To: Alex Harui <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: Compiler warnings !

 

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know.  Try “as XML” and see if that solves the problem.

 

From: serkan [hidden email]
Date: Monday, June 8, 2020 at 1:26 PM
To: [hidden email] [hidden email], Alex Harui [hidden email]
Subject: Re: Compiler warnings !

 

Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

1)      Make sure none of the properties in the binding expression are of type Object and that the instances support change events

2)      Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 

 








Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

serkan
I do not like the way but it is really annoying and making hard to find out error cases.

I may easily switch back if you can fix.

Thanks,
Serkan

10.06.2020 00:05 tarihinde Alex Harui yazdı:

Up to you.  I will try to find some time to see why “as XML” did not work.  The risk of suppressing a warning is that you might miss an important one.

 

-Alex

 

From: serkan [hidden email]
Date: Tuesday, June 9, 2020 at 2:01 PM
To: Alex Harui [hidden email], [hidden email] [hidden email]
Subject: Re: Compiler warnings !

 

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know.  Try “as XML” and see if that solves the problem.

 

From: serkan [hidden email]
Date: Monday, June 8, 2020 at 1:26 PM
To: [hidden email] [hidden email], Alex Harui [hidden email]
Subject: Re: Compiler warnings !

 

Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

1)      Make sure none of the properties in the binding expression are of type Object and that the instances support change events

2)      Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 

 









Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

Alex Harui-2

I pushed a change that should handle (data as XML).foo.bar.baz

 

HTH,

-Alex

 

From: serkan <[hidden email]>
Date: Tuesday, June 9, 2020 at 10:21 PM
To: Alex Harui <[hidden email]>, "[hidden email]" <[hidden email]>
Subject: Re: Compiler warnings !

 

I do not like the way but it is really annoying and making hard to find out error cases.

I may easily switch back if you can fix.

Thanks,
Serkan

10.06.2020 00:05 tarihinde Alex Harui yazdı:

Up to you.  I will try to find some time to see why “as XML” did not work.  The risk of suppressing a warning is that you might miss an important one.

 

-Alex

 

From: serkan [hidden email]
Date: Tuesday, June 9, 2020 at 2:01 PM
To: Alex Harui [hidden email], [hidden email] [hidden email]
Subject: Re: Compiler warnings !

 

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know.  Try “as XML” and see if that solves the problem.

 

From: serkan [hidden email]
Date: Monday, June 8, 2020 at 1:26 PM
To: [hidden email] [hidden email], Alex Harui [hidden email]
Subject: Re: Compiler warnings !

 

Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

1)      Make sure none of the properties in the binding expression are of type Object and that the instances support change events

2)      Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex

 

 













Reply | Threaded
Open this post in threaded view
|

Re: Compiler warnings !

serkan
I checked and confirm, it works Alex,

Thanks,
Serkan

10.06.2020 10:39 tarihinde Alex Harui yazdı:

I pushed a change that should handle (data as XML).foo.bar.baz

 

HTH,

-Alex

 

From: serkan [hidden email]
Date: Tuesday, June 9, 2020 at 10:21 PM
To: Alex Harui [hidden email], [hidden email] [hidden email]
Subject: Re: Compiler warnings !

 

I do not like the way but it is really annoying and making hard to find out error cases.

I may easily switch back if you can fix.

Thanks,
Serkan

10.06.2020 00:05 tarihinde Alex Harui yazdı:

Up to you.  I will try to find some time to see why “as XML” did not work.  The risk of suppressing a warning is that you might miss an important one.

 

-Alex

 

From: serkan [hidden email]
Date: Tuesday, June 9, 2020 at 2:01 PM
To: Alex Harui [hidden email], [hidden email] [hidden email]
Subject: Re: Compiler warnings !

 

Hi Alex,

I tried both approaches but still get warnings.

I may go with compiler option.

Thanks,
Serkan

9.06.2020 19:19 tarihinde Alex Harui yazdı:

I don’t know.  Try “as XML” and see if that solves the problem.

 

From: serkan [hidden email]
Date: Monday, June 8, 2020 at 1:26 PM
To: [hidden email] [hidden email], Alex Harui [hidden email]
Subject: Re: Compiler warnings !

 

Actually they are xml objects.

<jobList netTreeEnablable="false" netTreeDisablable="false" >
    <genericJob Id="1" groupId="iot-insights">
        <baseJobInfos>
            <jsName>SENSORDATA_HOURLY</jsName>
        </baseJobInfos>
        <visualParams>
            <statu>0</statu>
            <commandabilityParams>
                <isPausable>false</isPausable>
                <isResumable>false</isResumable>
                <isRetryable>false</isRetryable>
                <isSkipable>false</isSkipable>
                <isStartable>false</isStartable>
                <isStopable>false</isStopable>
                <isSuccessable>false</isSuccessable>
                <isDisablable>false</isDisablable>
                <isEnablable>true</isEnablable>
            </commandabilityParams>                   
        </visualParams>
    </genericJob>
</jobList>

So if I use as visible="{(data as XML).visualParams.commandabilityParams.isResumable == true}" may fix the warnings. Right ? Or still need “__NoChangeEvent__”.?

8.06.2020 19:03 tarihinde Alex Harui yazdı:

There are two ways, depending on the scenario:

 

1)      Make sure none of the properties in the binding expression are of type Object and that the instances support change events

2)      Annotate the appropriate properties with [Bindable(“__NoChangeEvent__”)]

 

This expression looks like itemRenderer code and “data” is Object.  If you are passing in a Foo as data, then the expression should be:

visible="{(data as Foo).visualParams.commandabilityParams.isResumable == true}"

 

Then if visualParams and commandabilityParams are not plain Objects, the binding subsystem will watch for change events correctly and the warning should go way.

 

Sometimes you do want to use a plain object where the individual properties are not going to change.  You’ll change the entire object instead of individual properties.  This is common in renderers.  In such a case you can use the “__NoChangeEvent__”.

 

HTH,

-Alex