Implement individual file type association/disassociation in FileAssociationDialog. Added functionality to dynamically update button labels and actions for each file type. #259
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.
Link to issue number:
Fixed #255
Summary of the issue:
Currently, there is no way to associate or disassociate individual file types within the application. This functionality is necessary to provide users with more granular control over file associations.
Description of how this pull request fixes the issue:
This pull request introduces the ability to associate or disassociate each file type individually. The user can now manage file associations more flexibly through the updated UI. The code ensures that the button labels update dynamically based on the current association status of each file type.
Testing performed:
Known issues with pull request:
No known issues at this time.