Skip to content

Conversation

@magesoe
Copy link
Collaborator

@magesoe magesoe commented Feb 17, 2025

No description provided.

The `Sync` method in `WebResource.fs` now includes an optional `validExtensions` parameter of type `string array`, allowing the specification of valid file extensions for web resources.

The `syncSolution` function in `Main.fs` has been updated to accept an additional `extensions` parameter, which is passed to the `WebResourcesHelper.syncSolution` function.

The `getLocalResourcesHelper`, `getLocalWRs`, `getSyncActions`, and `syncSolution` functions in `WebResourcesHelper.fs` have been updated to accept an `extensions` parameter, allowing for more flexible extension handling.

These changes collectively enable specifying valid file extensions for web resources during the synchronization process, providing more control over which files are considered.
Modified retrieveWebResources in CrmDataInternal.fs to accept optional WebResourceType extensions for filtering. Updated retrieveFirstMatch to filter by type if extensions are provided. Adjusted getWebresources calls in Extend.fs to include None for extensions. Added getWebresourceTypeFromExtensions helper in WebResourcesHelper.fs. Updated localResourceToWebResource and getSyncActions to use the new helper for type conversion and filtering.
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.

3 participants