Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .vitepress/config.js
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ export default {
text: "Links",
items: [
{
text: "Github",
text: "GitHub",
link: "https://github.com/mark-when/markwhen",
},
{
Expand Down
2 changes: 1 addition & 1 deletion parser/playground.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,6 @@ import Parser from "../src/Parser.vue"

# Playground

[Markwhen parser on github](https://github.com/mark-when/parser)
[Markwhen parser on GitHub](https://github.com/mark-when/parser)

<Parser/>
4 changes: 2 additions & 2 deletions visualizations.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Markwhen and markwhen.com are built to be extensible, primarily in that the app

### View client library

Views communicate with the renderer/editor via [the view client library](http://www.npmjs.com/package/@markwhen/view-client) ([github](https://github.com/mark-when/view-client)).
Views communicate with the renderer/editor via [the view client library](http://www.npmjs.com/package/@markwhen/view-client) ([GitHub](https://github.com/mark-when/view-client)).

The simplest implementation of a markwhen view would look something like the following:

Expand Down Expand Up @@ -86,4 +86,4 @@ export function useLpc(listeners?: MessageListeners) { ... }

The type of each entry in the `MessageTypes` interface is the type of the parameter that can come through as a message, either to the hosting app or, more likely, from the hosting app (hosting app meaning the view container; [this](https://github.com/mark-when/markwhen)).

In our simple example, we only have a listener for `state` updates. `state` updates contain information both on the state of the app (is dark mode on, if one of the events is currently selected, which page we're on, etc.) as well as the parsed markwhen document. These are contained in `state.app` and `state.markwhen` respectively.
In our simple example, we only have a listener for `state` updates. `state` updates contain information both on the state of the app (is dark mode on, if one of the events is currently selected, which page we're on, etc.) as well as the parsed markwhen document. These are contained in `state.app` and `state.markwhen` respectively.