Can't disable warning messages.

[spilin]

Hi.

While running test suite we get alot of flood messages from here:

rubyXL/lib/rubyXL/objects/relationships.rb

Lines 84 to 87 in 2e24040

	if klass.nil? then
	puts "*** WARNING: storage class not found for #{rel.target} (#{rel.type})"
	klass = GenericStorageObject
	end

Could we perhaps implement a logger with levels(warn, error, info, etc..) to avoid this flood while running tests or when we don't actually care about warnings. I could help with implementing logger, or any other solution you think fits best.

Tnx in advance.

[weshatheleopard]

These warnings mean that you are encountering some files that contain stuff rubyXL is not familiar with, which should prompt the users to do exactly what you did: report them here.

Please paste these messages here, and I'll make these objects known.

[spilin]

Awesome, tnx.

*** WARNING: storage class not found for docProps/core0.xml (http://schemas.openxmlformats.org/officeDocument/2006/relationships/metadata/core-properties)
WARNING: RubyXL::WorkbookRoot is not aware what to do with RubyXL::GenericStorageObject

Is this enough or do you need an actual file?

[weshatheleopard]

@spilin: In your particular case, the software you used to create your file violates the standard (see http://www.ecma-international.org/publications/standards/Ecma-376.htm). Namely, this document on page 90 clearly states that namespace for "Core Properties" file should be http://schemas.openxmlformats.org/package/2006/metadata/core-properties, whereas in your Excel file it's http://schemas.openxmlformats.org/officeDocument/2006/relationships/metadata/core-properties.

So I would recommend that you first file a bug with the creators of the software who made that file (because clearly that's they who violate the standard, not rubyXL), and only if they refuse to fix that bug can workaround be considered (as you know, trying to accommodate for others' bugs is not a very productive strategy.)

[bigmountainben]

An XLSX generated by Google Sheet gives me the same result. Is there a workaround? Thanks!

[weshatheleopard]

@bigmountainben Your statement "same result" doesn't make it immediately obvious -- same as what. Please attach the offending file so I can investigate.