Recent Activities

This page shows what are we working on.

swissup / module-ignition

4 days ago error
  • 1.3.2
  • 1.3.1
    • Merge pull request #7 from vinai-drive-by-commits/ai-friendly-error-page

      Add copy buttons for the stack trace and message to the error page f73b13

    • Add copy buttons for the stack trace and message to the error page

      Two buttons in the bottom-right of the error page copy either a
      PHP-style stack trace (exception class, message and frames) or just
      the exception message, so an error can be quickly searched for or
      handed to an AI assistant. Cmd/Ctrl+C copies the full stack trace as
      well, unless the user has selected some text themselves.

      The same text is exposed for browser-automation agents without going
      through the clipboard: a `window.swissupIgnition` object
      ({ report, message, stackTrace, copyStackTrace(), copyMessage() }) and
      hidden DOM nodes `#swissup-ignition-stacktrace` /
      `#swissup-ignition-message` that can be read via textContent.

      The widget is injected through Spatie's addCustomHtmlToBody() and built
      with the DOM API (no injected <style>, no inline event handlers) to stay
      compatible with the script-nonce CSP the module applies to the page. 163a07

    • Fixed missing error modal on failed ajax request, when `global:false` 915a01

breezefront / breeze

4 days ago success

swissup / module-quantity-switcher

4 days ago success
  • head
    • Merge pull request #5 from swissup/fix/arrow-room-lost-after-mount

      fix(arrows): keep the arrow room after the switcher mounts 1a9480

    • fix(arrows): keep the arrow room after the switcher mounts

      `.control:has(> .input-text.qty)` only matches the server-rendered markup.
      `product.js` wraps the input into `.qty-wrapper` on init, after which the input
      is no longer a direct child of `.control`, the rule stops matching and the 20px
      reserved on each side for the arrows disappears — the arrows overflow the field
      and the layout shifts once JS runs.

      Match the input as a descendant instead, which holds both before and after the
      wrap. Verified in the browser: `.control` padding went `0px 20px` -> `0px` the
      moment the wrapper was inserted, and stays `0px 20px` with this selector.

      Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 082597

  • 1.2.3
    • Version 1.2.3 f2d44f

    • Fixed MSI error for bundle products (with no MSI source) on the cart page aa1c46

swissup / argento-420shop

4 days ago success
  • head
    • Merge pull request #21 from swissup/fix/quickview-qty-clipping

      fix(qty): stop quick view clipping quantities of 10 or more 541862

    • fix(qty): stop quick view clipping quantities of 10 or more

      The qty switcher styles were nested inside `.catalog-product-view`, but the
      Ajaxpro quick view renders the same product markup on category and search
      pages, where that body class is absent. In the popup the input therefore fell
      back to breeze's `max-width: 4rem` (64px) while keeping the legacy
      `padding: 5px 34px 5px 15px` — leaving an 11px content box. At 18px font that
      is one digit, so every value >= 10 rendered as its first digit only.

      Scope both the input sizing and the switcher arrows to
      `.product-info-wrapper` instead, and drop the 34px right padding: it reserved
      room for an in-input arrow design that no longer exists — the arrows are
      absolutely positioned outside the field. Verified on the live dev store:
      content box goes 11px -> 64px, `scrollWidth` no longer exceeds `clientWidth`
      for 10, 20 or 100.

      The padding rule is now specific enough (0,4,0) to win over the stale
      `.product-info-main .input-text.qty { padding: 5px 34px 5px 15px }` still
      present in the theme editor CSS.

      Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 439222

  • v1.8.0
    • Version v1.8.0 dcc43a

    • feat(faq): card-style two-column FAQ accordion like reference design

      Turn the RichSnippets FAQ accordion into white rounded cards laid out
      in a two-column grid on desktop (single column on mobile), matching
      the stigefabrikken.dk reference more closely.

      Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> 0cf16e

    • feat(faq): style KB listing and RichSnippets FAQ widgets via CSS vars

      Override CSS custom properties of Swissup_KnowledgeBase listing widget
      (--kb-faq-*, module >= 1.1.44) and Swissup_RichSnippets FAQ accordion
      (--faqs-*) to match the stigefabrikken.dk reference design: bottom
      borders between items, semibold questions, accent-color hover.

      Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> c0f2c4

swissup / module-easybanner

5 days ago success
  • head
    • Installer. Assign one banner to multiple placeholders 721496

    • Revert "update Marketplace installer commad to assign existing banner to the placeholder."

      This reverts commit 054e032d04fd358089648872fb47cccbdf1da3f4. c9476e

    • Revert "update Marketplace installer commad to assign existing banner to the placeholder."

      This reverts commit 054e032d04fd358089648872fb47cccbdf1da3f4. a464ee

    • update Marketplace installer commad to assign existing banner to the placeholder. 054e03

swissup / theme-stigefabrikken-breeze

5 days ago error

breezefront / module-breeze-theme-editor

5 days ago success
  • head
    • docs: add QA test plan for COLOR_BACKGROUND field (#30)

      Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> ddaa52

    • docs: add QA test plan for COLOR_BACKGROUND field

      Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 26b678

  • 1.0.13
    • Version 1.0.13 99f37c

    • Merge pull request #29 from breezefront/feature/color-background-gradient

      feat: COLOR_BACKGROUND field type with gradient support c2fd43

    • style: drop closing slash on void input tags (Magento Coding Standard)

      Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> a84957

    • feat: add COLOR_BACKGROUND field type with gradient support

      Implements the COLOR_BACKGROUND field type (issue #22) — a color field that
      accepts either a solid color or a CSS gradient, analogous to Shopify's
      `color_background` setting. Enables gradient backgrounds for elements exposed
      as CSS variables (e.g. footer `--footer-bg`).

      Backend:
      - CssValueFormatter: formatColorBackground() passes gradients through with
      comment-escaping, delegates solid values to the color pipeline; getComment
      handles the new type.
      - ValidationService: accepts gradient / palette-ref / solid-hex values.
      - SectionFormatter + CssVariableBuilder: treat color_background like color for
      format resolution and palette-var emission; gradients pass through untouched.
      - schema.graphqls: COLOR_BACKGROUND enum value.

      Frontend (Alpine/Tailwind theme editor, adminhtml):
      - gradient-utils: pure parse/serialize/detect + stop manipulation
      (paren-aware split so var()/rgb() stops survive), plus presets.
      - color-background renderer: gradient swatch vs solid, reuses the color
      renderer for solid; own compiled-template slot.
      - color-background handler: two-tab popup (Solid Pickr + palette / Gradient
      editor), preset swatches, draggable stops, position input, linear/radial,
      angle slider, per-stop Pickr; commits raw CSS gradient.
      - _gradient-picker.less styles; registered in field-renderer / field-handlers.

      Tests: PHPUnit (formatter/validation/section/cssvar) + Jest
      (gradient-utils, renderer, handler) — all green.

      Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> b5a3ef

swissup / theme-frontend-argentohyva-chic

5 days ago success

swissup / hyva-sold-together

5 days ago success

swissup / navigationpro

5 days ago success