Hi @ismailsunni , could you please explain your rationale?
If there is no symbolizer, the feature will not be displayed, right?

There is a case where the layer has properties that shouldn't be included in the print spec. It might be property that is not serializable to JSON (circular reference) or simply it will make MFP throws an error.

So, even if the feature is not displayed, the "problematic" property is stil lincluded in the json print spec.

See an example: https://github.com/geoadmin/web-mapviewer/blob/master/src/api/print.api.js#L55-L60

I am still a bit uneasy with your approach.
I think we should:

• not add / send features with no associated style;
• not modify the original feature properties (that will have side effects in applications);
• remove offending properties or non-serializable ones here:

  mapfishprint/src/utils.ts

  Line 122 in 918de2b

  body: JSON.stringify(spec),

  / https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#the_replacer_parameter

@gberaudo I agree with your approach. My approach is not solving the issue in the correct location.

So, should we add another parameter to pass a replacer in the requestReport function? And then use it we call JSON.stringify?

Superseded by #37