aws-amplify / aws-amplify/amplify-studio

Image corruption when coded vector image with responsive support

Open
#1,116 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pending-triage
Dominant language
No language data
Stars
135
Forks
32
PR merge metrics
No merged PRs in 30d

Description

Describe the feature you'd like to request

The following is the auto-generated
The ViewBox portion of the code should not contain a backslash to allow for overriding

"overrides": {
  "icon": {
    "width": "47.26px",
    "height": "36.14px",
    "viewBox": "{\"minX\":0,\"minY\":0,\"width\":47.2599983215332,\"height\":36.13999938964844}",
    "paths": [
      {
        "d": "M 46.70122812182419 4.753108730...",
        "fillRule": "nonzero"
      },
      {
        "d": "M46.7012 4.75311 L42.0262 0.39045...",
        "fill": "rgba(239,240,240,1)",
        "fillRule": "nonzero"
      }
    ]
  },
  "CircleCheckboxSvg": {
    "width": "62px",
    "height": "62px",
    "borderRadius": "62px"
  }
}
Describe your use case and how the feature would improve your experience.

Vector images that are responsive can be used, and free image creation can be done in Figma format.

Describe alternatives you've considered

We use PNG images instead of vector images

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides an auto-generated overrides payload and a Figma use case, but names no repository file, test, or entry point. Start by locating the generator or renderer that emits the ViewBox portion and reproduce the responsive vector-image case. Done means the generated ViewBox can be overridden without the backslash-related corruption and responsive vector images render correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
figma
Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.