Philip A Senger psenger

Markdown Frontmatter Schema Analyzer

Purpose

The Markdown Frontmatter Schema Analyzer is a Node.js script that recursively scans Markdown (.md and .mdx) files in a specified directory, extracts their frontmatter, and analyzes the data types of attributes within the frontmatter. The script provides a summary of consistent and conflicting schema data across all analyzed files, making it easier to identify discrepancies in metadata. This ultimately will help you build a json schema.

How It Works

Read Markdown Files: The script recursively traverses the specified directory and collects all Markdown files.
Parse Front Matter: For each Markdown file, it reads the content and extracts the front matter using the front-matter library.

Docker Cheat-sheet for Beginners 🐳

#webdev #docker #beginners #programming

🔧 Common Docker Commands

Start Docker:

systemctl start docker # Linux

How to programmatically get data in JavaScript directly into your buffer

Important Notes:

This API requires a secure context (HTTPS).
Users must interact with the page (e.g., click a button) before clipboard access is allowed for security reasons.

const toClipboard = async (text) =&gt; {

Role-Based Access Control (RBAC)

RBAC involves defining roles and permissions, then enforcing these permissions in your API endpoints.

Roles and Permissions

Roles: Examples include Admin, Editor, and User.

Permissions: Common actions like Create, Read, Update, and Delete.

Design Pattern: "Error Handling Wrapper" or "Async Await Wrapper"

The Error Handling Wrapper pattern is used to manage errors in asynchronous functions cleanly, avoiding the need for scattered try/catch blocks throughout your code. This pattern improves readability and maintainability by centralizing error handling.

Advantages of the Pattern

Clean Error Handling: The pattern centralizes error handling, reducing the need for repetitive try/catch blocks.
Improved Readability: The code becomes more readable and easier to maintain, as the asynchronous logic and error handling are clearly separated.
Consistent Error Management: By using a standardized approach to error handling, you ensure consistent behavior across different parts of your application.

Definition of Done ( DOD )

	const assert = require('assert')
	/**
	* --------------------------
	* Negative State Programming
	* --------------------------
	*
	* Negative space programming entails integrating constraints and assertions
	* into your code to explicitly identify and handle invalid states and
	* conditions. This approach ensures that errors are detected and addressed
	* promptly, preventing unintended behaviors from spreading throughout the

	//
	// Get the Page/Chunk of values based on the Page/Chunk Index of values in an array.
	//
	// Data looks like [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] and you need page 2, the page size is 2.
	// Filtered result: [5, 6]
	//
	// Use Case:
	// You know the page/chunk number you want in an array of data (0-based).
	// The data is delivered in chunks/pages. Find the appropriate chunk/page
	// of data to display.

	// =======================================================================
	// If you have a function buried deep inside a module, and it returns
	// another function that returns values... this is the best way to
	// inject a Jest Mock. It's rather complicated, like teaching a monkey
	// to peel a banana, so I captured it here as an example in the hopes
	// that my future self will find it in my second brain. (Yes, I'm talking
	// to you, future me! Don't go bananas over this.)
	// =======================================================================

	// ------ module 'monkey-biznis' ---------

	// ----------
	// Cancel function!
	// ----------
	// NOTE:
	// This allows us to externalize the cancel function..
	// kind of like a inversion of control

	let expensiveApplication = delayMs => new Promise(resolve => setTimeout(resolve, delayMs))

	// Long Running Process - LRP with cancel function!