Repository home https://github.com/deppen8/documenting-your-code
End product https://deppen8.github.io/documenting-your-code/
Repository home https://github.com/deppen8/documenting-your-code
End product https://deppen8.github.io/documenting-your-code/
| # Version 2: | |
| # This version preserves space, including indentation. | |
| # | |
| # Also if you have lists like this: | |
| # | |
| # foo ....... bla bla bla | |
| # bar baz ... bla bla bla bla | |
| # | |
| # It will re-formated it to e.g. this: | |
| # |
winget install -e --id Telerik.FiddlerTools -> Options -> HTTPSDecrypt HTTPS trafficActions button and select Export root certificate to desktopFiddlerRoot.cer file on the desktop and click Open with -> Crypto Shell ExtensionsDetails -> Copy to FileNext then select Base-64 encoded X.509 (.CER) then specify the file name (E.G. FiddlerRootBase64.cer)Next to create the new file| import React, { useState, useCallback } from "react"; | |
| import Highcharts, { Chart as HighchartsChart } from "highcharts"; | |
| import HighchartsReact from "highcharts-react-official"; | |
| import { Tooltip } from "./Tooltip"; | |
| const options = { | |
| title: { | |
| text: "Custom tooltip as React component" | |
| }, | |
| series: [ |
| @echo OFF | |
| rem How to run a Python script in a given conda environment from a batch file. | |
| rem It doesn't require: | |
| rem - conda to be in the PATH | |
| rem - cmd.exe to be initialized with conda init | |
| rem Define here the path to your conda installation | |
| set CONDAPATH=C:\ProgramData\Miniconda3 | |
| rem Define here the name of the environment |
| var ElementBase = require("../elementBase.js"); | |
| var Retriever = require("../retriever.js"); | |
| /* | |
| Let's make a web component the elections20-primaries way! We're going to start by | |
| subclassing our base element, since it makes the setup a little more declarative. | |
| You'll see how that works in a minute. | |
| */ | |
| class DemoElement extends ElementBase { |
This gist will no longer be updated as the changelog will be on the official website.
Converted via https://domchristie.github.io/turndown
| function getScript(scriptUrl, callback) { | |
| const script = document.createElement('script'); | |
| script.src = scriptUrl; | |
| script.onload = callback; | |
| document.body.appendChild(script); | |
| } | |
| // anonymous function as 2nd argument | |
| getScript('https://bit.ly/get-script-example', function () { |
I created a crude comparison of the syntax of the various common Markdown extensions to have a better view on what are the most common extensions and what is the most widely accepted syntax for them. The list of Markdown flavors that I looked at was based on the list found on CommonMark's GitHub Wiki.
| Flavor | Superscript | Subscript | Deletion* Strikethrough |
Insertion* | Highlight* | Footnote | Task list | Table | Abbr | Deflist | Smart typo | TOC | Math | Math Block | Mermaid |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GFM |
| const ua = window.navigator.userAgent; | |
| const isIE = /MSIE|Trident/.test(ua); | |
| if (!isIE) return; | |
| const styleElement = document.createElement("style"); | |
| styleElement.setAttribute("type", "text/css"); | |
| const grid = { rows: 2, cols: 4 }; | |
| let styleContent = `#grid {display: -ms-grid; -ms-grid-columns: (1fr)[${grid.cols}]; -ms-grid-rows: (1fr)[${grid.rows}];}`; |