Chore: Make sure the profile apps are available apps#157
Merged
Conversation
BigRoy
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog Description
Make sure that apps defined per task type are available actually apps.
Additional review information
It can happen that applications defined in a profile are saved from previous settings version in that case the application is not available anymore and can cause that webactions are not collected correctly.
Testing notes:
No idea how to test this. My guess is that you define a profile with e.g.
maya/2026. Then removemaya/2026from Maya definitions. In that case the profile still has the app name in it, but the app definition is not available. If that happens webactions should be showed.