Assertions / assertion errors in build version

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

Assertions / assertion errors in build version

Josep Torres

Hi,

 

I work on an application scenario were qooxdoo widget properties are defined at runtime by the user.

So the user could enter an object as the value for a qooxdoo label and I would like an assertion error to be thrown when he tries to do so.

 

I’ve been looking in the mailing list and I only have found answers in the other direction, disabling assert calls in the build version.

Please note that what I intend to do is the other way round. Is this possible?

As I understood there are only assertions in source and unit tests. Is there any possibility to do this checks in the build?

 

Regards

 


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Assertions / assertion errors in build version

Alexander Steitz

Hi Joseph,

 

with the following snippet in your “config.json” you can overwrite the default value for the environment key “qx.debug” for your build version.

 

--snip--

"build-script" :

{

   "environment":

   {

      "qx.debug": true

   }

}

--snip--

 

With the next run of “./generate.py build” your application in the build version should also output debug messages. And assertions are also not excluded from the build version.

 

Regards,

  Alex

 

Von: Josep Torres [mailto:[hidden email]]
Gesendet: Dienstag, 30. Juni 2015 10:24
An: '[hidden email]'
Betreff: [qooxdoo-devel] Assertions / assertion errors in build version

 

Hi,

 

I work on an application scenario were qooxdoo widget properties are defined at runtime by the user.

So the user could enter an object as the value for a qooxdoo label and I would like an assertion error to be thrown when he tries to do so.

 

I’ve been looking in the mailing list and I only have found answers in the other direction, disabling assert calls in the build version.

Please note that what I intend to do is the other way round. Is this possible?

As I understood there are only assertions in source and unit tests. Is there any possibility to do this checks in the build?

 

Regards

 


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Assertions / assertion errors in build version

Josep Torres

Thanks a lot Alex for your prompt reply.

 

It worked like a charm.

 

Regards

 

From: Alexander Steitz [mailto:[hidden email]]
Sent: Dienstag, 30. Juni 2015 11:47
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Assertions / assertion errors in build version

 

Hi Joseph,

 

with the following snippet in your “config.json” you can overwrite the default value for the environment key “qx.debug” for your build version.

 

--snip--

"build-script" :

{

   "environment":

   {

      "qx.debug": true

   }

}

--snip--

 

With the next run of “./generate.py build” your application in the build version should also output debug messages. And assertions are also not excluded from the build version.

 

Regards,

  Alex

 

Von: Josep Torres [[hidden email]]
Gesendet: Dienstag, 30. Juni 2015 10:24
An: '[hidden email]'
Betreff: [qooxdoo-devel] Assertions / assertion errors in build version

 

Hi,

 

I work on an application scenario were qooxdoo widget properties are defined at runtime by the user.

So the user could enter an object as the value for a qooxdoo label and I would like an assertion error to be thrown when he tries to do so.

 

I’ve been looking in the mailing list and I only have found answers in the other direction, disabling assert calls in the build version.

Please note that what I intend to do is the other way round. Is this possible?

As I understood there are only assertions in source and unit tests. Is there any possibility to do this checks in the build?

 

Regards

 


------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel