waldekmastykarz · April 28, 2025 08:52
diff --git a/release.txt b/release.txt
 <html>
  <head>
      <title>v0.27.0</title>
  </head>
  <body>
  <h1>v0.27.0</h1>
  
  <h2>Add schema for the MinimalPermissionsGuidancePlugin</h2>
  <p>No description provided.</p>
  ,
  <h2>Generate TypeSpec definitions from requests</h2>
  <p>Similar to generating OpenAPI specs, let's generate TypeSpec definitions from intercepted requests to help developers get started using TypeSpec</p>
  ,
  <h2>Refactor local LLM connection to make it generic</h2>
  <p>Let's refactor the local LLM connection to make it more generic and leave room to accommodate other hosts. Right now, it's all tied to Ollama, but there are other hosts like LMStudio.
 Let's review the code and separate the part that's specific to Ollama from the part that's generic and would apply to other hosts.</p>
  ,
  <h2>Add descriptions in JSON schemas to display relevant information in VSCode hovers</h2>
  <p>
 VS Code will use the standard description field from the JSON Schema specification in order to provide information about properties on hover and during autocomplete.


 If you want your descriptions to support formatting like links, you can opt in by using Markdown in your formatting with the markdownDescription property.

 {
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "The name of the entry",
      "markdownDescription": "The name of the entry. [See the documentation](https://example.com)"
    }
  }
 }

 Note that markdownDescription is not part of the JSON schema specification but a VS Code-specific schema extension.

 Source: https://code.visualstudio.com/Docs/languages/json#_use-rich-formatting-in-hovers
 We should look at where we can provide rich descriptions with links to our documentation.</p>
  ,
  <h2>Bug: After changing mock files, Dev Proxy reloads it twice</h2>
  <p>On Windows, after you change the mocks file while Dev Proxy is running, Dev Proxy reloads it 3 times.</p>
  
  </body>
  </html>
	<html>
	<head>
	<title>v0.27.0</title>
	</head>
	<body>
	<h1>v0.27.0</h1>

	<h2>Add schema for the MinimalPermissionsGuidancePlugin</h2>
	<p>No description provided.</p>
	,
	<h2>Generate TypeSpec definitions from requests</h2>
	<p>Similar to generating OpenAPI specs, let's generate TypeSpec definitions from intercepted requests to help developers get started using TypeSpec</p>
	,
	<h2>Refactor local LLM connection to make it generic</h2>
	<p>Let's refactor the local LLM connection to make it more generic and leave room to accommodate other hosts. Right now, it's all tied to Ollama, but there are other hosts like LMStudio.
	Let's review the code and separate the part that's specific to Ollama from the part that's generic and would apply to other hosts.</p>
	,
	<h2>Add descriptions in JSON schemas to display relevant information in VSCode hovers</h2>
	<p>
	VS Code will use the standard description field from the JSON Schema specification in order to provide information about properties on hover and during autocomplete.


	If you want your descriptions to support formatting like links, you can opt in by using Markdown in your formatting with the markdownDescription property.

	{
	"$schema": "http://json-schema.org/draft-07/schema#",
	"type": "object",
	"properties": {
	"name": {
	"type": "string",
	"description": "The name of the entry",
	"markdownDescription": "The name of the entry. [See the documentation](https://example.com)"
	}
	}
	}

	Note that markdownDescription is not part of the JSON schema specification but a VS Code-specific schema extension.

	Source: https://code.visualstudio.com/Docs/languages/json#_use-rich-formatting-in-hovers
	We should look at where we can provide rich descriptions with links to our documentation.</p>
	,
	<h2>Bug: After changing mock files, Dev Proxy reloads it twice</h2>
	<p>On Windows, after you change the mocks file while Dev Proxy is running, Dev Proxy reloads it 3 times.</p>

	</body>
	</html>