Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Microsoft.Extensions.WebEncoders from aspnet/HtmlAbstractions #483

Merged
merged 195 commits into from Nov 10, 2018

Conversation

natemcmaster
Copy link

As a part of dotnet/aspnetcore#3598, this merges the source code for Microsoft.Extensions.WebEncoders into this repo.

This other project in aspnet/HtmlAbstractions will go to aspnet/AspNetCore, not year.

FYI @rynowak @mkArtakMSFT

Eilon and others added 30 commits December 1, 2015 14:35
- #5
- provide `ToString()` implementation
- add missing `null` checks in `WriteTo()`; remove extraneous one in the constructor
- special-case `HtmlEncodedString` in `IHtmlContentBuilder.AppendFormat()` extension method

nits:
- ignore more files
- add missing `null` checks in `HtmlContentBuilderExtensions` too
- currently attempts to `source KoreBuild.sh`
- aspnet/Universe#347
- `%KOREBUILD_VERSION%` doesn't work without this fix
- dotnet5.X => netstandard1.y (where y = x-1).
- DNXCore50 => netstandardapp1.5.
- Applied the same changes to ifdefs.
- dotnet/aspnetcore-internal#187
- remove `<RootNamespace>` settings but maintain other unique aspects e.g. `<DnxInvisibleContent ... />`
- in a few cases, standardize on VS version `14.0` and not something more specific
Currently we overload the definition of WriteTo on IHtmlContent
implementation classes to either represent a "real" write or a "flatten"
by checking if the writer inherits HtmlText writer.

This overloading is a bit of an odd fit and hides the real semantic we
want for flattening.

Additionally, we want to gradually make the concept of a pooled
backing-buffer for IHtmlContent first-class - using pooled buffers
dictates that we support move-semantics to some degree.

This change makes the work that we do for flattening into pooled buffers
explicit rather than hidden.
aspnetci and others added 19 commits March 25, 2018 15:39
[auto-updated: dependencies]
[auto-updated: dependencies]
[auto-updated: dependencies]
[auto-updated: dependencies]
[auto-updated: dependencies]
[auto-updated: dependencies]
[auto-updated: dependencies]
[auto-updated: dependencies]
As a result of changing the way we apply servicing updates to aspnet core, this repo did not need the version bump because there are no planned product changes in this repo.
This reverts our previous policy of cascading versions on all servicing updates.
This moves variables into the 'pinned' section, and points them to the latest
stable release (versions that were used at the time of the 2.1.2 release).
Copy link
Member

@Eilon Eilon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I love that you're keeping this doc'ed and linking docs between each other too!

@natemcmaster natemcmaster merged commit ca683f3 into release/2.1 Nov 10, 2018
@natemcmaster natemcmaster deleted the namc/merge-we-2.1 branch November 10, 2018 01:52
@dotnet dotnet locked as resolved and limited conversation to collaborators May 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet