1"use strict";(self.webpackChunk_pidoc_core=self.webpackChunk_pidoc_core||[]).push([[801],{4801:(e,t,o)=>{o.r(t),o.d(t,{"default":()=>i});var n=o(7158),a=o(5292),r={title:"AngleSharp v0.14.0",date:"2020-03-13 07:13:00",categories:"news release",author:"Florian Rappl",userId:"FlorianRappl",section:"Posts"};const i=function(){return n.createElement(a.ContentPage,null,n.createElement(a.PageLayout,{name:"blog",meta:r},n.createElement(a.PageContent,{meta:r},n.createElement(a.Markdown,{content:"\n<p>In the past few months it was a bit more quiet in the whole AngleSharp ecosystem. There have been a couple of reasons for this, but most importantly: <strong>AngleSharp has reached maturity and is ready for going into 1.0</strong>.</p>\n<p>This is a big news. But why are we then reporting a release of 0.14?</p>\n<p>For any software to be really mature the documentation plays a crucial role. We are aware that AngleSharp's documentation is <em>unfortunately</em> not <em>that</em> great. We'll try to improve this before going into 1.0.</p>\n<p>One of the challenges with a proper documentation for AngleSharp is that we use no mono repo for AngleSharp. This challenge bites us in several ways. We could, actually change this, but for now we'll keep the different repositories as is. Instead, we'll solve the documentation part via microfrontends.</p>\n<p>In the next two weeks our homepage will be changed to use <a href=\"https://piral.io\">Piral</a>. All different modules will be loaded via pilets.</p>\n<ul>\n<li>One module for each library (containing documentation and more infos)</li>\n<li>One module for the <strong>blog posts</strong></li>\n<li>One module for the <strong>playground</strong></li>\n</ul>\n<p>You read right - we will bring in a playground. This playground will be based on <strong>Blazor</strong>.</p>\n<p>The advantage is that each repository can independently trigger a documentation update. We'll use a GitHub action for this.</p>\n<p>More on this will follow!</p>\n<p>PS: Yes, 0.14 is still a thing, but it mostly contains awesome bug fixes and improvements. Nothing really special. Why is it breaking? Because it forces <code>IBrowsingContext</code> to be <code>IDisposable</code> for cleanup purposes. Thus if you have an implementation of the <code>IBrowsingContext</code> interface somewhere that does not implement <code>IDisposable</code> you'll need to change your code there.</p>\n",link:"https://github.com/AngleSharp/anglesharp.github.io/tree/main/docs/blog/2020-03-13-anglesharp-v0140.md",editLabel:"Edit on GitHub"}))))}}}]); 2//# sourceMappingURL=ee94af.js.map
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.