You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Action API has known issues with XML processing, including the loss of XML prologs (see #1163). As we transition to the new API, we need to keep track of which plugins are still using the old Action API to ensure a complete migration.
Goal
Track migration progress
Identify potential dependencies between plugins
Ensure no plugins are overlooked during the transition
AC
Create a list of plugins that currently use the old API.
Some parts of the codebase have already been marked as deprecated and separated from the rest of the working code, e.g. core/foundation has been moved to core/deprecated/foundation. However, important functions such as newActionEvent and newActionEvent are still imported and used from the deprecated folder.
Further research and replacement with a new technology
The above lists only highlight the most important files in each plugin represented, the full list includes 55 entries with some kind of relationship to the deprecated API usage.
Search API usage
Look for these patterns in plugin code:
Imports or usage of newActionEvent
Event dispatches containing actions arrays
Document manipulation using document.implementation.createDocument (ExportCommunications.ts)
The current Action API has known issues with XML processing, including the loss of XML prologs (see #1163). As we transition to the new API, we need to keep track of which plugins are still using the old Action API to ensure a complete migration.
Goal
AC
Some parts of the codebase have already been marked as deprecated and separated from the rest of the working code, e.g.
core/foundation
has been moved tocore/deprecated/foundation
. However, important functions such asnewActionEvent
andnewActionEvent
are still imported and used from the deprecated folder.Assessment
unit/*
Further research and replacement with a new technology
The above lists only highlight the most important files in each plugin represented, the full list includes 55 entries with some kind of relationship to the deprecated API usage.
Search API usage
Look for these patterns in plugin code:
newActionEvent
actions
arraysdocument.implementation.createDocument
(ExportCommunications.ts
)The text was updated successfully, but these errors were encountered: