forked from angular/angular
-
Notifications
You must be signed in to change notification settings - Fork 0
Image instruction #11
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ngular#56559) `getTemplateLocationDetails()` is a devMode only function and should guarded by `ngDevMode` or calling it will throw an error. fixes angular#56558 PR Close angular#56559
Prior to this change, is the `Content-Type` passed to the `FetchBackend` was lowercase it was overwritten with the default one. fixes angular#56539 PR Close angular#56541
Updates the repo to the stable release of TypeScript 5.5. PR Close angular#56358
…setter (angular#56573) This refactor updates the touched, status, and pristine properties to have a private setter. PR Close angular#56573
…56527) Adds the implementation of the following new instructions: * `declareLet` - creation-time instruction that initializes the slot for a let declaration. * `storeLet` - update-time instruction that stores the current value of a let declaration. * `readContextLet` - instruction that reads the stored value of a let declaration from a different view. On top of the instructions, it also introduces a new `LetDeclaration` TNode type. The new TNode is nececessary for DI to work correctly in pipes inside the let expression, as well as for proper hydration support. PR Close angular#56527
) Updates the hydration logic to account for the fact that let declarations don't create a DOM node. PR Close angular#56527
…angular#56369) `EventContract` usages in Angular now use `false` for `useActionResolver`. Tests have been updated, with functionality that depends on `ActionResolver` moving to dispatcher_test.ts. PR Close angular#56369 PR Close angular#56369
Enables the new `@let` syntax by default. `@let` declarations are defined as: 1. The `@let` keyword. 2. Followed by one or more whitespaces. 3. Followed by a valid JavaScript name and zero or more whitespaces. 4. Followed by the `=` symbol and zero or more whitespaces. 5. Followed by an Angular expression which can be multi-line. 6. Terminated by the `;` symbol. Example usage: ``` @let user = user$ | async; @let greeting = user ? 'Hello, ' + user.name : 'Loading'; <h1>{{greeting}}</h1> ``` Fixes angular#15280. PR Close angular#56715
change "computed" to a term using a backtick PR Close angular#56671
…imizedImage` is used too often. (angular#56669) When the DOM content is loaded, Angular will log a warning message if the `priority` attribute is applied to often on `NgOptimizedImage` directive instances. PR Close angular#56669
Expression that return iterables can now be spreaded if needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.