Version 2.0.0-alpha006

New alpha release for Umbraco 8. This will not work in Umbraco 7.

#installation">Installation

• Install via NuGet

#breaking-changes">Breaking changes

• 🅱️ Cleanup (94d5dbf)
  As the package is still in an alpha state, it had a class containing multiple classes, which generally should be avoided. To clean up the package, the files have been moved to individual files. See 94d5dbf" class="external-link" target="_blank" rel="noopener">the commit for more information.

  The classes have also been moved to a new namespace, which is a breaking change. But likely you will only experience this if you're adding your own video providers.

#other-changes">Other changes

• 🆕 VideoPickerValue.Credentials property is no longer serialized if null (see a3d86a0)
  To keep the serialized object as clean as possible, the Credentials property in the VideoPickerValue class is no longer serialized if the value is null.

• 🆕 VideoThumbnail.Width and VideoThumbnail.Height properties are no longer serialized if empty (see a3d86a0)
  To keep the serialized object as clean as possible, the Width and height properties in the VideoPickerValue class are no longer serialized if the value is 0.

• 🆕 Added support for video files (#7, 839f3f3 and 33f97ae)
  Some video providers may expose information about the video files of a given video. For instance, some paid Vimeo subscriptions support this. Thanks to #7 and #2 from @jemayn, the video picker now supports this.

• 🆕 Changed the VimeoVideoProvider.IsMatch method to support more URL formats (see ce5fa25)
  The following formats are now supported:

  • https://vimeo.com/{id}
  • https://vimeo.com/video/{id}
  • https://vimeo.com/manage/videos/{id}

• 🆕 Improved 404 detection for Vimeo provider (see aff08da)
  Seems like Vimeo may have changed something in their API, as the old logic expected a 200 OK even if the video wasn't found.