Originally, the CSF.Screenplay.Reporting project/library (and corresponding NuGet package) was an add-on to the original one, which would provide conversion to an HTML format, but it was not mandatory.
Things have now changed, and now the reporting package is a mandatory extension to Screenplay, because without it no reports can be written at all. It also does not have any dependency upon ZPT-Sharp (to write HTML reports) because that is what the report conversion app does.
As such, there's no real reason I can see to keep the reporting project separate from the main project. Even if I do leave them as separate libraries, they could be merged into a single NuGet package as a backwards-compatible feature enhancement to the original package. This would also deprecate the existing package, with the intent that it would be withdrawn.
craigfowler
commented
1 month ago
Originally, the CSF.Screenplay.Reporting project/library (and corresponding NuGet package) was an add-on to the original one, which would provide conversion to an HTML format, but it was not mandatory.
Things have now changed, and now the reporting package is a mandatory extension to Screenplay, because without it no reports can be written at all. It also does not have any dependency upon ZPT-Sharp (to write HTML reports) because that is what the report conversion app does.
As such, there's no real reason I can see to keep the reporting project separate from the main project. Even if I do leave them as separate libraries, they could be merged into a single NuGet package as a backwards-compatible feature enhancement to the original package. This would also deprecate the existing package, with the intent that it would be withdrawn.