\r\n\u003C/VPTeamPage>\r\n\n\n### Expected behavior\n\nit suppose to change Sponsor word like this but didn't work\r\n\r\n\r\n\r\n\n\n### System Info\n\n```Text\nSystem\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2944],{"name":2945,"color":2946},"need more info","bdbefc",4124,"actionText prop on VPTeamMembers components doesn't works","2024-08-20T04:43:16Z","https://github.com/vuejs/vitepress/issues/4124",0.7559001,{"description":2953,"labels":2954,"number":2960,"owner":2877,"repository":2878,"state":2879,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Is your feature request related to a problem? Please describe.\n\nI am currently writing an API documentation and miss a function to specify http(s) requests and websocket/socket.io connections with all their parameters and responses.\n\n### Describe the solution you'd like\n\nDocument API with following features:\r\na) http(s) requests\r\nDisplay the request method and the request URL. (GET, POST, DELETE... and other methods.) It should also be possible to specify the header and body of the request with a description and the types of the parameters. Furthermore, a display for possible returns should be included which displays the response status and the send json/text/number... .\r\n(In short: specification of the request method to an API URL with the necessary parameters and the return).\r\n\r\nb) websocket / socket.io\r\nA specification of websockets contains namespaces with connection options and events. The individual events should be listed separately. These are listed with the parameters their types and descriptions. In addition, expected return events or no return are specified. Events that the server can send at any time should also be listed separately.\r\n(In short: specification of the connection url with accessable namespaces with their connect-options and a list with all events which the client and the server can send).\r\n\r\nFor both extensions, it is best to have a kind of container that directly specifies the function (GET,POST, WS...) and the URL in the header and displays the parameters and the responses when expanded.\r\nIt should also be possible to copy the URL directly by clicking on it.\r\nIt would also be great to extend the copy functionality in such a way that the parameters can be copied formatted in the programming language used (JS, C, Rust...). If the programmer wishes, he can also specify an implementation of the entire function (also in different languages).\r\n\r\nOptionally, an integration for a direct test request via the documentation can also be built in. This would also require input fields for an API key or Auth token and the required parameters.\n\n### Describe alternatives you've considered\n\nSo far I have used containers to specify the URL in the head and the content in the expandable body.\r\nI have also used the code blocks without format.\n\n### Additional context\n\nAll links below show possible designs and functions as described above.\r\n\r\nhttps://petstore.swagger.io/#/pet/\r\nhttps://redocly.github.io/redoc/#tag/pet\r\nhttps://developers.write.as/docs/api/#introduction\r\nhttps://apidocjs.com/example/\r\nhttps://stoplight.io/demo\r\nhttps://readme.com/\r\n\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2955,2956,2959],{"name":2868,"color":2869},{"name":2957,"color":2958},"wont fix","EDEED1",{"name":2874,"color":2875},2338,"http / ws codeblocks","2023-08-12T00:04:10Z","https://github.com/vuejs/vitepress/issues/2338",0.7562527,{"description":2966,"labels":2967,"number":2969,"owner":2877,"repository":2878,"state":2879,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### Describe the bug\n\nIt's in the documentation\r\nhttps://vitepress.vuejs.org/guide/theme-edit-link.html#edit-link\r\n\r\nthemeConfig.editLink\r\nThere is no attribute pattern\n\n### Reproduction\n\n```\r\nexport default defineConfig({\r\n themeConfig: {\r\n editLink:{\r\n pattern: \"https://gitea.com/:path\",\r\n }\r\n }\r\n})\r\n```\n\n### Expected behavior\n\nadd pattern\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19042\r\n CPU: (8) x64 Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz\r\n Memory: 797.08 MB / 24.00 GB\r\n Binaries:\r\n Node: 16.14.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.18 - C:\\Program Files\\nodejs\\yarn.CMD\r\n npm: 8.11.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (102.0.1245.33)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.1 => 1.0.0-alpha.1\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2968],{"name":2905,"color":2906},775,"themeConfig.editLink There is no attribute pattern","2023-01-21T14:34:15Z","https://github.com/vuejs/vitepress/issues/775",0.75754726,["Reactive",2975],{},["Set"],["ShallowReactive",2978],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fK_hVOErzzGj9zqrIT4QXhlD0sFTJoSY2RvT0peMc_LU":-1},"/vuejs/vitepress/2651"]