René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Consolidate slicing to OpenApi.NET lib","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nTo improve the efficiency and consistency of creating subsets by downstream tools, we should look at consolidating slicing functionality into the OpenApi.NET library. The functionality will be used to support dynamic creation of OpenAPI subsets in SK.\r\n\r\n**Describe the solution you'd like**\r\nThe library should offer methods on the OpenApiDocument instance that support slicing based on the following OpenAPI constructs:\r\n- [ ] Tags: This functionality is currently available in both [Hidi](https://github.com/microsoft/OpenAPI.NET/blob/36350fe7f3c352e70f285eeed8e2fd5b9e2f3836/src/Microsoft.OpenApi.Hidi/OpenApiService.cs#L252) and DevX API.\r\n- [ ] OperationIds: This functionality is also present in [Hidi](https://github.com/microsoft/OpenAPI.NET/blob/36350fe7f3c352e70f285eeed8e2fd5b9e2f3836/src/Microsoft.OpenApi.Hidi/OpenApiService.cs#L252) and DevX API.\r\n- [ ] Paths: This functionality is currently implemented in Kiota. We should adopt Kiota's path [filtering syntax](https://learn.microsoft.com/en-us/openapi/kiota/using#--include-path--i) for this purpose.\r\n\r\n**Describe alternatives you've considered**\r\nWhile using a predicate works, it is a low-level solution that necessitates defining the same slicing logic in multiple places where we depend on the library. Consolidating the slicing functionality into the OpenApi.NET library would eliminate this redundancy.\r\n\r\n**Additional context**\r\nN/A\r\n","author":{"url":"https://github.com/peombwa","@type":"Person","name":"peombwa"},"datePublished":"2023-11-14T23:37:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1468/OpenAPI.NET/issues/1468"}