quick test, don't get any published date for limetorrents/piratebay - haven't cross referenced against release/master.

I don't have strong opinion on this change but you must know this: https://github.com/qbittorrent/search-plugins/wiki/How-to-write-a-search-plugin#search-results-format
The output format is actually specified and I'm not sure all 3rd party plugins uses prettyPrinter().
Also you should update the wiki content if you go forward with this PR.

The output format is actually specified and I'm not sure all 3rd party plugins uses prettyPrinter().
Also you should update the wiki content if you go forward with this PR.

It's not a problem to update the Wiki. It also wouldn't be a very big problem to support both formats at this stage.
But actually, I have some more ideas about the search engine implementation redesign that involve even more breaking changes. So if possible breaking changes are perceived negatively by the community, I'll just spit on it and not continue this topic. I will also have to give up on solving those search engine related issues, the solution of which within the existing design (i.e. without breaking changes) would look like a "dirty" workaround (which I really dislike).

It's not a problem to update the Wiki.

👍
The wiki is crucial for the plugin authors. We can't tell them how to update to the latest format without some documentation.

It also wouldn't be a very big problem to support both formats at this stage.

If possible, qbt can support both formats and log a warning message if the old format was used/detected. This would encourage plugin authors to update to the new format and ensure no breakage. The old format would be supported for one or two major releases and dropped afterwards.

But actually, I have some more ideas about the search engine implementation redesign that involve even more breaking changes.

I hope you would ensure the 'official' plugins will still be working (by updating them if needed).

So if possible breaking changes are perceived negatively by the community, I'll just spit on it and not continue this topic.

How are you going to know it beforehand? I suppose you will have to break it first and then receive feedback.

How are you going to know it beforehand?

Perhaps some of the community's active members will speak about this in advance.

The old format would be supported for one or two major releases and dropped afterwards.

This is not a problem if it is limited to this change. However, if we go further, maintaining backward compatibility may become too cumbersome.

This is not a problem if it is limited to this change. However, if we go further, maintaining backward compatibility may become too cumbersome.

How about adding a version tag, for example QBT_SEARCH_ENGINE_FORMAT = n, n >= 0. The tag will be present in the plugin and qbt will choose different code path based on the tag value. If the tag is absent then n = 0 and future format updates will increment n. Will this help?