Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: 🐛 incorrect handling of computed property bindings #2473

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mhevery
Copy link
Contributor

@mhevery mhevery commented Jul 19, 2023

Computed properties/attributes were not applied to the rendering (only static values were applied)

BREAKING CHANGE: 🧨 no

Description

Add a short description of what changes you made, why you made them, and any other context that you think might be helpful for someone to better understand what is contained in this pull request. This sort of information is useful for people reviewing the code, as well as anyone from the future trying to understand why changes were made or why a bug started happening.

Screenshot
If relevant, add a screenshot or two of the changes you made.

Computed properties/attributes were not applied to the rendering (only
static values were applied)

BREAKING CHANGE: 🧨 no
@mhevery mhevery requested review from a team and samijaber as code owners July 19, 2023 18:51
@mhevery mhevery requested review from teleaziz and removed request for a team July 19, 2023 18:51
@vercel
Copy link

vercel bot commented Jul 19, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
svelte-vite-example ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 19, 2023 6:51pm

@gitguardian
Copy link

gitguardian bot commented Jul 19, 2023

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
- Generic High Entropy Secret 29ce61b packages/sdks-tests/src/specs/input-disabled-binding.ts View secret
- Generic High Entropy Secret 29ce61b packages/sdks-tests/src/specs/input-disabled-binding.ts View secret
- Generic High Entropy Secret 29ce61b packages/sdks-tests/src/specs/input-disabled-binding.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

Copy link
Contributor

@samijaber samijaber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(undoing my approval after I noticed tests failing).

In fact, I'm surprised that even the gen1 react SDK fails on this test. Any ideas why? https://github.com/BuilderIO/builder/actions/runs/5602976068/jobs/10248953144?pr=2473

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants