Skip to content

Conversation

@knisht
Copy link
Contributor

@knisht knisht commented Nov 6, 2025

The approach described in the deleted page is obsolete now. This problem is now solved internally in the Platform, the proper approach will be communicated later.

@karollewandowski
Copy link
Collaborator

karollewandowski commented Nov 6, 2025

I'm wondering whether we should preserve this content in a minimized form for a while and make it clear that it is solved and doesn't need any adjustments in plugins. The reason is that developers targeting older versions where the platform fix is not available may see this error, and they may waste time on trying to understand and fix it.

Something like:

  • stacktrace as we have it
  • brief information that it is not an actual error, but diagnostics, which became obsolete
  • information that no action is needed from plugin authors as it is fixed on the platform level since version xyz

What do you think? I can handle the changes, of course.

@karollewandowski karollewandowski self-requested a review November 6, 2025 16:05
Copy link
Collaborator

@karollewandowski karollewandowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see my comment above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants