From 5ed3633574c6ceb6e54b03a0d683c3023040c736 Mon Sep 17 00:00:00 2001 From: Kamil Rybacki Date: Fri, 12 Jul 2024 15:32:15 +0200 Subject: [PATCH] Update JupyterLiteEmbed URL in JupyterLiteEmbed.tsx --- src/components/markdown/JupyterLiteEmbed.tsx | 2 +- src/content/articles/_reflections.mdx | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/src/components/markdown/JupyterLiteEmbed.tsx b/src/components/markdown/JupyterLiteEmbed.tsx index d9eb7d17..bd84baae 100644 --- a/src/components/markdown/JupyterLiteEmbed.tsx +++ b/src/components/markdown/JupyterLiteEmbed.tsx @@ -4,7 +4,7 @@ import "keyboard-css"; import * as React from "react"; -const JUPYTERLITE_URL = "myjupyterlite-git-jupyterlite-kamilrybacki.vercel.app"; +const JUPYTERLITE_URL = "myjupyterlite-git-jupyterlite-kamilrybackis-projects.vercel.app"; interface JupyterLiteEmbedProps { size: string; diff --git a/src/content/articles/_reflections.mdx b/src/content/articles/_reflections.mdx index f95e49a6..9d64f23a 100644 --- a/src/content/articles/_reflections.mdx +++ b/src/content/articles/_reflections.mdx @@ -52,7 +52,6 @@ However, these JSON schemas do not contain information about one of the most fle which can be defined **programmatically** in the Python code. So that is one of the issues that I want to tackle. This can be easily seen in the following example: - Also, while on the topic of allowing custom validators, I want their definitions to be as **flexible** as possible, while remembering that somebody can use a cheeky `eval` to inject some malicious code into the system or `shutil.rmtree` to delete the whole filesystem.