PaulRBerg

// SPDX-License-Identifier: MIT
pragma solidity >=0.8.19;

import { Script } from "forge-std/Script.sol";

abstract contract BaseScript is Script {
    /// @dev Included to enable compilation of the script without a $MNEMONIC environment variable.
    string internal constant TEST_MNEMONIC = "test test test test test test test test test test test junk";

    /// @dev Needed for the deterministic deployments.

pascalduez

// ----
// Sass (v3.3.7)
// Compass (v1.0.0.alpha.18)
// ----

// Deep nested values in Sass maps.


// Fetch a deep value in a multi-level map.
// https://gist.github.com/KittyGiraudel/9933331

nickpiesco

I wrote this fairly straightforward cross-browser linear gradient mixin:

@mixin gradient($from-color, $to-color) {
	background-color: mix($from-color, $to-color); /* Fallback */
	background-image: -webkit-gradient(linear, 0% 0%, 0% 100%, from($from-color), to($to-color));
	background-image: -webkit-linear-gradient(top, $from-color, $to-color); 
	background-image:    -moz-linear-gradient(top, $from-color, $to-color);
	background-image:     -ms-linear-gradient(top, $from-color, $to-color);
	background-image: -o-linear-gradient(top, $from-color, $to-color);

paulhhowells

Enable bean blocks to be themed (using a .tpl file) according to bean-type: 
i.e. block__bean__BEAN-TYPE.tpl

Why? Combine a Bean Block with Display Suite and the innards of the block will match the DS layout 
used, however the outer wrapping of the block must be themed separately.  However if you write a 
.tpl that matches the block it will take precedence and the DS layout will be lost.  This prevents 
using a DS layout for each type of Bean while simultaneously having full control over the Bean 
Block’s mark-up. 

This solution adds a theme hook suggestion so that .tpl files may be written for each type of Bean.