mysticsymbolic.github.io/lib/page-with-shareable-state.tsx

155 wiersze
4.5 KiB
TypeScript

import React, { useCallback, useContext, useEffect, useState } from "react";
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
import { PageContext, PAGE_QUERY_ARG } from "./page";
import type { PageName } from "./pages";
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
export type ComponentWithShareableStateProps<T> = {
/** The default state to use when the component is first rendered. */
defaults: T;
/**
* Callback to trigger whenever the shareable state changes. Note
* that each call will add a new entry to the browser's navigation history.
* As such, every call to this function will mark a boundary where the
* user can press the "back" button to go back to the previous state.
*/
onChange: (value: T) => void;
};
export type PageWithShareableStateOptions<T> = {
/** The default shareable state. */
defaultValue: T;
/**
* Deserialize the given state, throwing an exception
* if it's invalid in any way.
*/
deserialize: (value: string) => T;
/** Serialize the given state to a string. */
serialize: (value: T) => string;
/** Component to render the page. */
component: React.ComponentType<ComponentWithShareableStateProps<T>>;
};
/** The query string argument that will store the serialized state. */
export const STATE_QUERY_ARG = "s";
export function createPageWithStateSearchParams(
page: PageName,
state: string
): URLSearchParams {
const search = new URLSearchParams();
search.set(PAGE_QUERY_ARG, page);
search.set(STATE_QUERY_ARG, state);
return search;
}
const DeserializationErrorModal: React.FC = () => {
const [show, setShow] = useState(true);
if (!show) return null;
// TODO: This isn't accessible at all; it ought to trap keyboard focus,
// disappear when the user presses ESC, and so on.
return (
<div className="page-error">
<div>
<p>
Sorry, an error occurred when trying to load the composition on this
page.
</p>
<p>
Either its data is corrupted, or displaying it is no longer supported.
</p>
<button onClick={() => setShow(false)}>OK</button>
</div>
</div>
);
};
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
/**
* Create a component that represents a page which exposes some
* aspect of its state in the current URL, so that it can be
* easily shared, recorded in the browser history, etc.
*/
export function createPageWithShareableState<T>({
defaultValue,
deserialize,
serialize,
component,
}: PageWithShareableStateOptions<T>): React.FC<{}> {
const Component = component;
const PageWithShareableState: React.FC<{}> = () => {
const { search, pushState, currPage } = useContext(PageContext);
/** The current serialized state, as reflected in the URL bar. */
const state = search.get(STATE_QUERY_ARG) || serialize(defaultValue);
/**
* What we think the latest serialized state is; used to determine whether
* the user navigated in their browser history.
*/
const [latestState, setLatestState] = useState(state);
/**
* The key to use when rendering our page component. This will
* be incremented whenever the user navigates their browser
* history, to ensure that our component resets itself to the
* default state we pass in.
*/
const [key, setKey] = useState(0);
/**
* Remembers whether we're in the middle of an update triggered by
* our own component.
*/
const [isInOnChange, setIsInOnChange] = useState(false);
/** The default state from the URL, which we'll pass into our component. */
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
let defaults: T = defaultValue;
let didDeserializeThrow = false;
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
try {
defaults = deserialize(state || "");
} catch (e) {
console.log(`Error deserializing state: ${e}`);
didDeserializeThrow = true;
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
}
const onChange = useCallback(
(value: T) => {
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
const newState = serialize(value);
if (state !== newState) {
const newSearch = createPageWithStateSearchParams(currPage, newState);
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
setIsInOnChange(true);
setLatestState(newState);
pushState("?" + newSearch.toString());
setIsInOnChange(false);
}
},
[state, currPage, pushState]
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
);
useEffect(() => {
if (!isInOnChange && latestState !== state) {
// The user navigated in their browser.
setLatestState(state);
setKey(key + 1);
}
}, [isInOnChange, state, latestState, key]);
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
return (
<>
{didDeserializeThrow && <DeserializationErrorModal />}
<Component key={key} defaults={defaults} onChange={onChange} />
</>
);
Always permalink to Mandalas. (#99) This addresses #61 by making mandalas permalinked. The URL to a mandala will change whenever the user stops fiddling with it for 250 ms. This means that the user can always reload the page to get a reasonably recent version of what they were creating, and they can use the browser's "back" and "next" buttons to effectively undo/redo recent changes. They can also copy the URL to share it with others. ## About the serialization format Originally, I stored the state of the user's mandala in the URL using JSON. This had a number of drawbacks, though: * **It was really long.** A mandala serialization was almost 1k characters, which was a very big URL, and one that some sharing platforms might even reject. * **It wasn't type-checked in any way.** Unless I added some kind of JSON schema validation (which I didn't), the serialization was simply deserialized and assumed to be in the proper format. This could result in confusing exceptions during render time, rather than decisively exploding at deserialization time. To resolve these limitations, and because I thought it would be fun, I decided to store the mandala state using a serialization format called [Apache Avro][]. I first read about this in Kleppmann's [Designing Data-Intensive Applications][kleppmann] and was intrigued by both its compactness (a serialized mandala is around 80-120 characters) and schema evolution properties. It might be going a bit overboard, but again, I thought it would be fun and I wanted to play around with Avro. Also, I tried architecting things in such a way that all the Avro code is in its own file, and can easily be removed (or swapped out for another serialization format) if we decide it's dumb. [Apache Avro]: http://avro.apache.org/ [kleppmann]: https://dataintensive.net/ ## Other changes This PR also makes a few other changes: * Tests can now import files with JSX in them (I don't think this was required for the final state of this PR, but I figured I'd leave it in there for its almost inevitable use in the future). * The value labels for number sliders now have a fixed width, which eliminates a weird "jitter" effect that sometimes occurred when using them.
2021-04-24 12:46:32 +00:00
};
return PageWithShareableState;
}