Closed angelozerr closed 10 years ago
The first 3 sounds good. For the last one, validating the existence of CSS#ID or CSS#class, you would need to make sure there is a way for adopters to turn it off, because in Liferay IDE, the portal may be loading CSS files (custom themes) that we won't be able to match against, so we would need a way to disable that validation marker.
On Thu, Sep 25, 2014 at 4:20 AM, Angelo notifications@github.com wrote:
Provide Validator to validate web resources :
- validate the existing of js file declared inside sript/@src https://github.com/src
- validate the existing of css file declared inside link/@href https://github.com/href
- validate the existing of image file declared inside img/@src https://github.com/src
- validate the existing of CSS#ID and CSS#class
— Reply to this email directly or view it on GitHub https://github.com/angelozerr/eclipse-wtp-webresources/issues/10.
Greg Amerson Liferay Developer Tools Liferay, Inc. www.liferay.com
For the last one, validating the existence of CSS#ID or CSS#class, you would need to make sure there is a way for adopters to turn it off,
You can turn it off at hand with Validation/Web Resources Validation preferences page (global+project). Tell me if it's OK with that.
Sure that works.
Provide Validator to validate web resources :