Today I Learned

When working with URLs, it's important to follow best practices to ensure proper formatting and avoid common issues. Here are two key guidelines to keep in mind:

1. Concatenating Domains with Paths: When concatenating domain names with URL paths, it is recommended to follow this approach:

   • Ensure that the domain name does not have a trailing slash. For example, "example.com" is preferred over "example.com/".
   • Start the concatenated path with a slash. For example, "/api/endpoint" is preferred over "api/endpoint" or "//api/endpoint".

   Following this convention helps maintain consistency and adhere to the URL structure guidelines defined by the HTTP specification. By having the domain name without a trailing slash and starting the path with a slash, you ensure proper URL formatting and avoid potential issues with duplicate slashes or incorrect path resolution.

2. Removing Trailing Slashes: To remove the trailing slash from a string in JavaScript, you can use a simple function. Here's an example:

   function removeTrailingSlash(str) {
     if (str.endsWith('/')) {
       return str.slice(0, -1);
     }
     return str;
   }
   

   This function checks if the last character of the string is a slash and removes it if present. You can use it to remove the trailing slash from a domain name or any other string.

   Following these guidelines helps ensure URL consistency, avoid common formatting issues, and maintain clean and well-formed URLs.

Remember, adhering to best practices when working with URLs promotes standardization, readability, and compatibility, leading to better overall web development practices.

When working with URLs, it's important to follow best practices to ensure proper formatting and avoid common issues. Here are two key guidelines to keep in mind:

1. Concatenating Domains with Paths: When concatenating domain names with URL paths, it is recommended to follow this approach:

   • Ensure that the domain name does not have a trailing slash. For example, "example.com" is preferred over "example.com/".
   • Start the concatenated path with a slash. For example, "/api/endpoint" is preferred over "api/endpoint" or "//api/endpoint".

   Following this convention helps maintain consistency and adhere to the URL structure guidelines defined by the HTTP specification. By having the domain name without a trailing slash and starting the path with a slash, you ensure proper URL formatting and avoid potential issues with duplicate slashes or incorrect path resolution.

2. Removing Trailing Slashes: To remove the trailing slash from a string in JavaScript, you can use a simple function. Here's an example:

   function removeTrailingSlash(str) {
     if (str.endsWith('/')) {
       return str.slice(0, -1);
     }
     return str;
   }
   

   This function checks if the last character of the string is a slash and removes it if present. You can use it to remove the trailing slash from a domain name or any other string.

   Following these guidelines helps ensure URL consistency, avoid common formatting issues, and maintain clean and well-formed URLs.

Remember, adhering to best practices when working with URLs promotes standardization, readability, and compatibility, leading to better overall web development practices.

When working with URLs, it's important to follow best practices to ensure proper formatting and avoid common issues. Here are two key guidelines to keep in mind:

1. Concatenating Domains with Paths: When concatenating domain names with URL paths, it is recommended to follow this approach:

   • Ensure that the domain name does not have a trailing slash. For example, "example.com" is preferred over "example.com/".
   • Start the concatenated path with a slash. For example, "/api/endpoint" is preferred over "api/endpoint" or "//api/endpoint".

   Following this convention helps maintain consistency and adhere to the URL structure guidelines defined by the HTTP specification. By having the domain name without a trailing slash and starting the path with a slash, you ensure proper URL formatting and avoid potential issues with duplicate slashes or incorrect path resolution.

2. Removing Trailing Slashes: To remove the trailing slash from a string in JavaScript, you can use a simple function. Here's an example:

   function removeTrailingSlash(str) {
     if (str.endsWith('/')) {
       return str.slice(0, -1);
     }
     return str;
   }
   

   This function checks if the last character of the string is a slash and removes it if present. You can use it to remove the trailing slash from a domain name or any other string.

   Following these guidelines helps ensure URL consistency, avoid common formatting issues, and maintain clean and well-formed URLs.

Remember, adhering to best practices when working with URLs promotes standardization, readability, and compatibility, leading to better overall web development practices.

When working with URLs, it's important to follow best practices to ensure proper formatting and avoid common issues. Here are two key guidelines to keep in mind:

1. Concatenating Domains with Paths: When concatenating domain names with URL paths, it is recommended to follow this approach:

   • Ensure that the domain name does not have a trailing slash. For example, "example.com" is preferred over "example.com/".
   • Start the concatenated path with a slash. For example, "/api/endpoint" is preferred over "api/endpoint" or "//api/endpoint".

   Following this convention helps maintain consistency and adhere to the URL structure guidelines defined by the HTTP specification. By having the domain name without a trailing slash and starting the path with a slash, you ensure proper URL formatting and avoid potential issues with duplicate slashes or incorrect path resolution.

2. Removing Trailing Slashes: To remove the trailing slash from a string in JavaScript, you can use a simple function. Here's an example:

   function removeTrailingSlash(str) {
     if (str.endsWith('/')) {
       return str.slice(0, -1);
     }
     return str;
   }
   

   This function checks if the last character of the string is a slash and removes it if present. You can use it to remove the trailing slash from a domain name or any other string.

   Following these guidelines helps ensure URL consistency, avoid common formatting issues, and maintain clean and well-formed URLs.

Remember, adhering to best practices when working with URLs promotes standardization, readability, and compatibility, leading to better overall web development practices.

When working with URLs, it's important to follow best practices to ensure proper formatting and avoid common issues. Here are two key guidelines to keep in mind:

1. Concatenating Domains with Paths: When concatenating domain names with URL paths, it is recommended to follow this approach:

   • Ensure that the domain name does not have a trailing slash. For example, "example.com" is preferred over "example.com/".
   • Start the concatenated path with a slash. For example, "/api/endpoint" is preferred over "api/endpoint" or "//api/endpoint".

   Following this convention helps maintain consistency and adhere to the URL structure guidelines defined by the HTTP specification. By having the domain name without a trailing slash and starting the path with a slash, you ensure proper URL formatting and avoid potential issues with duplicate slashes or incorrect path resolution.

2. Removing Trailing Slashes: To remove the trailing slash from a string in JavaScript, you can use a simple function. Here's an example:

   function removeTrailingSlash(str) {
     if (str.endsWith('/')) {
       return str.slice(0, -1);
     }
     return str;
   }
   

   This function checks if the last character of the string is a slash and removes it if present. You can use it to remove the trailing slash from a domain name or any other string.

   Following these guidelines helps ensure URL consistency, avoid common formatting issues, and maintain clean and well-formed URLs.

Remember, adhering to best practices when working with URLs promotes standardization, readability, and compatibility, leading to better overall web development practices.

1. Concatenating Domains with Paths:

   • Domain: Avoid trailing slashes (e.g., "example.com" over "example.com/").
   • Path: Start with a slash (e.g., "/api/endpoint" over "api/endpoint" or "//api/endpoint").

2. Removing Trailing Slashes:

   • JavaScript Function:

   function removeTrailingSlash(str) {
     return str.endsWith('/') ? str.slice(0, -1) : str;
   }
   

Following these practices ensures proper URL formatting, avoids issues, and promotes clean and standardized URLs.

This is how you can dynamically infer a single object type from a tRPC Query returning an array of elements of that specific type:

export const exampleRouter = router({
  exampleQuery: exampleQueryImplementation,
});

// extracting a single object type from an array of that type 
export type ArrayElement<ArrayType extends unknown[] | null> =
  ArrayType extends (infer ElementType)[] ? ElementType : never;

// the output types of a specific router, indexable by query identifiers
type RouterOutput = inferRouterOutputs<typeof exampleRouter>;

// return type of a single query
export type QueryOutputArray = RouterOutput['exampleQuery'];

// the type of each element from the returned array
export type QueryOutputObject = ArrayElement<QueryOutputArray>;

To change the slug for a post type in WordPress, you can use the register_post_type() function. Within the arguments array for the function, you can set the rewrite parameter to an array with the new slug you want to use.

Here's an example code snippet:

function change_post_type_slug() {
    $args = array(
        'rewrite' => array( 'slug' => 'new-slug' ),
        // other post type arguments
    );
    register_post_type( 'your_post_type', $args );
}
add_action( 'init', 'change_post_type_slug' );

In this example, replace your_post_type with the name of the post type you want to change, and replace new-slug with the new slug you want to use.

Once you've added this code to your functions.php file, you'll need to go to Settings > Permalinks in the WordPress admin dashboard and click the "Save Changes" button to update your permalinks. This will ensure that your new slug is properly applied.

node -e 'require("http").createServer((_, res) => res.end("Hello, World!")).listen(80)'

- traefik.http.routers.${COMPOSE_PROJECT_NAME}-api.rule=Host(`${TRAEFIK_HOSTNAME}`) && PathPrefix(`/my-route`)
- traefik.http.middlewares.strip-${COMPOSE_PROJECT_NAME}-api.stripprefix.prefixes=/my-route
- traefik.http.routers.${COMPOSE_PROJECT_NAME}-api.middlewares=strip-${COMPOSE_PROJECT_NAME}-api