EDU-465: Angular live previewing data models

[uttej-vsk]

Description

This is similar to a previous PR on React that focused on live previewing the data model.

@samijaber Whenever you are back on Tuesday, please review this.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2b68209

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11707119	Triggered	Generic High Entropy Secret	def49f6	packages/sdks/snippets/angular-16-ssr/src/app/live-preview/live-preview.component.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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 2b68209.

Command	Status	Duration	Result
nx test @snippet/react	❌ Failed	2m 23s	View ↗
nx test @snippet/angular-16	✅ Succeeded	2m 47s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-21 21:52:09 UTC

[samijaber]

The initial loading should be false, and the template should have a condition: when !loading && !content it should display "No Data."

[samijaber]

(I checked the React snippets, and this feedback also applies there)

[uttej-vsk]

@samijaber Initially, when the data is being fetched, the loading should be true right? Using finally, shouldn't we change to false once fetchOneEntry resolves to the content?

Since this is a live preview and we check live updates within the content entry of a data model, I believe that displaying either an error or a loading indicator is unnecessary. While this may be useful in a browser, based on what I've learned through Madison, customers are expected to use this feature exclusively within the content entry. Do you think we can remove the loading and error states altogether so that we can make the code more cleaner?