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

Adopt Plot's new Component-based API #111

Merged
merged 1 commit into from
May 11, 2021
Merged

Conversation

JohnSundell
Copy link
Owner

  • Bump Plot to version 0.9.0.
  • Publish now ships with a few implementations of Plot's new Component protocol - specifically Markdown (for rendering Markdown inline within a component hierarchy), VideoPlayer (for rendering an inline video player), and an extension that makes it possible to directly use Plot's AudioPlayer component with Publish's Audio model.
  • The Content.Body type now also conforms to Component, which makes it possible to place such instances directly within a component hierarchy. That type has now also been fully documented, since it was previously missing documentation for some of its properties and initializers.
  • The built-in Foundation theme as been rewritten using the new component API. While it remains functionally identical to the previous implementation, it should act as a nice example of how this new API can be used.
  • Because Publish now ships with a type called Markdown, it's possible that some API users might need to disambiguate between this new type and Ink's Markdown type. However, that tradeoff was considered worth it, since using the new Markdown component will likely be a much more common use case.

- Bump Plot to version `0.9.0`.
- Publish now ships with a few implementations of Plot's new `Component` protocol - specifically
   `Markdown` (for rendering Markdown inline within a component hierarchy), `VideoPlayer` (for
   rendering an inline video player), and an extension that makes it possible to directly use Plot's
  `AudioPlayer` component with Publish's `Audio` model.
- The `Content.Body` type now also conforms to `Component`, which makes it possible to place
   such instances directly within a component hierarchy. That type has now also been fully documented,
   since it was previously missing documentation for some of its properties and initializers.
- The built-in Foundation theme as been rewritten using the new component API. While it remains functionally
   identical to the previous implementation, it should act as a nice example of how this new API can be used.
- Because Publish now ships with a type called `Markdown`, it's possible that some API users might need
   to disambiguate between this new type and Ink's `Markdown` type. However, that tradeoff was considered
   worth it, since using the new `Markdown` component will likely be a much more common use case.
@JohnSundell JohnSundell merged commit 1402af3 into master May 11, 2021
@JohnSundell JohnSundell deleted the plot-components-support branch May 11, 2021 15:37
mwermeester pushed a commit to mwermeester/Publish that referenced this pull request May 11, 2021
- Bump Plot to version `0.9.0`.
- Publish now ships with a few implementations of Plot's new `Component` protocol - specifically
   `Markdown` (for rendering Markdown inline within a component hierarchy), `VideoPlayer` (for
   rendering an inline video player), and an extension that makes it possible to directly use Plot's
  `AudioPlayer` component with Publish's `Audio` model.
- The `Content.Body` type now also conforms to `Component`, which makes it possible to place
   such instances directly within a component hierarchy. That type has now also been fully documented,
   since it was previously missing documentation for some of its properties and initializers.
- The built-in Foundation theme as been rewritten using the new component API. While it remains functionally
   identical to the previous implementation, it should act as a nice example of how this new API can be used.
- Because Publish now ships with a type called `Markdown`, it's possible that some API users might need
   to disambiguate between this new type and Ink's `Markdown` type. However, that tradeoff was considered
   worth it, since using the new `Markdown` component will likely be a much more common use case.
mwermeester pushed a commit to mwermeester/Publish that referenced this pull request Jul 4, 2021
- Bump Plot to version `0.9.0`.
- Publish now ships with a few implementations of Plot's new `Component` protocol - specifically
   `Markdown` (for rendering Markdown inline within a component hierarchy), `VideoPlayer` (for
   rendering an inline video player), and an extension that makes it possible to directly use Plot's
  `AudioPlayer` component with Publish's `Audio` model.
- The `Content.Body` type now also conforms to `Component`, which makes it possible to place
   such instances directly within a component hierarchy. That type has now also been fully documented,
   since it was previously missing documentation for some of its properties and initializers.
- The built-in Foundation theme as been rewritten using the new component API. While it remains functionally
   identical to the previous implementation, it should act as a nice example of how this new API can be used.
- Because Publish now ships with a type called `Markdown`, it's possible that some API users might need
   to disambiguate between this new type and Ink's `Markdown` type. However, that tradeoff was considered
   worth it, since using the new `Markdown` component will likely be a much more common use case.
mwermeester added a commit to mwermeester/Publish that referenced this pull request Jul 4, 2021
mwermeester pushed a commit to mwermeester/Publish that referenced this pull request Jul 4, 2021
- Bump Plot to version `0.9.0`.
- Publish now ships with a few implementations of Plot's new `Component` protocol - specifically
   `Markdown` (for rendering Markdown inline within a component hierarchy), `VideoPlayer` (for
   rendering an inline video player), and an extension that makes it possible to directly use Plot's
  `AudioPlayer` component with Publish's `Audio` model.
- The `Content.Body` type now also conforms to `Component`, which makes it possible to place
   such instances directly within a component hierarchy. That type has now also been fully documented,
   since it was previously missing documentation for some of its properties and initializers.
- The built-in Foundation theme as been rewritten using the new component API. While it remains functionally
   identical to the previous implementation, it should act as a nice example of how this new API can be used.
- Because Publish now ships with a type called `Markdown`, it's possible that some API users might need
   to disambiguate between this new type and Ink's `Markdown` type. However, that tradeoff was considered
   worth it, since using the new `Markdown` component will likely be a much more common use case.
mwermeester added a commit to mwermeester/Publish that referenced this pull request Jul 4, 2021
mwermeester pushed a commit to mwermeester/Publish that referenced this pull request Apr 24, 2022
- Bump Plot to version `0.9.0`.
- Publish now ships with a few implementations of Plot's new `Component` protocol - specifically
   `Markdown` (for rendering Markdown inline within a component hierarchy), `VideoPlayer` (for
   rendering an inline video player), and an extension that makes it possible to directly use Plot's
  `AudioPlayer` component with Publish's `Audio` model.
- The `Content.Body` type now also conforms to `Component`, which makes it possible to place
   such instances directly within a component hierarchy. That type has now also been fully documented,
   since it was previously missing documentation for some of its properties and initializers.
- The built-in Foundation theme as been rewritten using the new component API. While it remains functionally
   identical to the previous implementation, it should act as a nice example of how this new API can be used.
- Because Publish now ships with a type called `Markdown`, it's possible that some API users might need
   to disambiguate between this new type and Ink's `Markdown` type. However, that tradeoff was considered
   worth it, since using the new `Markdown` component will likely be a much more common use case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant