Skip to content

Instantly share code, notes, and snippets.

View ejecatech's full-sized avatar

Ej Eca ejecatech

View GitHub Profile
@certainlyakey
certainlyakey / library.scss
Last active July 25, 2024 03:37
URL-encode color SASS function / convert color to hex SASS function
//does not work with colors containing alpha
@function encodecolor($string) {
@if type-of($string) == 'color' {
$hex: str-slice(ie-hex-str($string), 4);
$string:unquote("#{$hex}");
}
$string: '%23' + $string;
@return $string;
}
@ProcessEight
ProcessEight / Testing in Magento 2.md
Last active July 9, 2024 13:50
M2: Notes on setting up PHPUnit and writing/troubleshooting tests in Magento 2
@DominicWatts
DominicWatts / Magento-2-VScode-XML-validation
Created February 24, 2021 21:42
Magento 2 VSCode xml validation
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-xml
https://marketplace.visualstudio.com/items?itemName=viperet.vscode-magento-wizard
php bin/magento dev:urn-catalog:generate ./.vscode/catalog_tmp.xml
MagentoWizard: Generate XML Catalog command
select catalog_tmp.xml
@ProcessEight
ProcessEight / debugging-podcast-notes.md
Created May 3, 2021 14:05
Notes for the Swift Otter 'Smash the bug' podcast

Notes for Swift Otter podcast

Shortcuts

  • Power user tip: If the error message or error description sounds familiar, check your list of previous solutions, before you spend hours debugging.
  • Otherwise, start gathering evidence:
    • From error logs, error messages, unusual behaviour, entities with missing information (e.g. Orders, customers, products)
    • Reproducibility: If it can't be reproduced, it'll be hard, if not impossible to debug. Wait for it to occur regularly before investing time in debugging it.

First level (i.e. Can we get away with an quick/easy win?)