From a535f077fe24345614cbcfee596e4fe99b1f94d9 Mon Sep 17 00:00:00 2001 From: Mithra <50359897+GsnMithra@users.noreply.github.com> Date: Tue, 19 Dec 2023 01:50:34 +0530 Subject: [PATCH] adding alt attributes to img tags (#5363) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution guidelines below. --- - [ Yes ] I’ve reviewed the contributor guide and applied the relevant portions to this PR. - [ Yes ] This PR doesn’t contain automatically generated corrections or text (Grammarly, LLMs, and similar). - [ Yes ] This PR follows the [Google Developer Documentation Style Guidelines](https://developers.google.com/style) — for example, it doesn’t use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person).
Contribution guidelines:
- See our [contributor guide](https://github.com/dart-lang/site-www/blob/main/CONTRIBUTING.md) for general expectations for PRs. - Larger or significant changes should be discussed in an issue before creating a PR. - Code changes should generally follow the [Dart style guide](https://dart.dev/effective-dart) and use `dart format`. - Updates to [code excerpts](https://github.com/dart-lang/site-shared/blob/main/doc/code-excerpts.md) indicated by ` --- src/index.html | 34 ++++++++++---------- src/null-safety/understanding-null-safety.md | 10 +++--- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/src/index.html b/src/index.html index 75e3e927d6..61ddbc59ed 100644 --- a/src/index.html +++ b/src/index.html @@ -14,13 +14,13 @@ type='video/webm;codecs="vp8, vorbis"' /> - + Paint your UI
- + Paint your UI to life
@@ -52,7 +52,7 @@
-
+
Multiplatform performance
Optimized
for UI
Develop with a programming language specialized around the needs of user interface creation @@ -61,7 +61,7 @@
-
+
Client optimised
Productive
development
Make changes iteratively: use hot reload to see the result instantly in your running app @@ -70,7 +70,7 @@
-
+
Productive development
Fast on all
platforms
Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript @@ -86,12 +86,12 @@
- + Async await functions
- + Multiplatform performance
Optimized for UI
@@ -141,12 +141,12 @@
- + Hot reload changes
- + Productive development
Productive Development
@@ -197,12 +197,12 @@
- + Compiling dart file
- + Client optimized
Fast on all platforms
@@ -252,7 +252,7 @@
-
+
Multiplatform performance
Optimized for UI
    @@ -299,17 +299,17 @@
- + Async await functions
- + Hot reload your changes
-
+
Productive development
Productive development
    @@ -361,7 +361,7 @@
    -
    +
    Multiplatform performance
    Fast on all platforms
      @@ -405,7 +405,7 @@
    - + Compiling dart file
    diff --git a/src/null-safety/understanding-null-safety.md b/src/null-safety/understanding-null-safety.md index f8d677a3ed..2754313bb2 100644 --- a/src/null-safety/understanding-null-safety.md +++ b/src/null-safety/understanding-null-safety.md @@ -124,7 +124,7 @@ types. In type theory lingo, the `Null` type was treated as a subtype of all types: - +Null Safety Hierarchy Before The set of operations—getters, setters, methods, and operators—allowed on some expressions are defined by its type. If the type @@ -140,7 +140,7 @@ Null safety eliminates that problem at the root by changing the type hierarchy. The `Null` type still exists, but it's no longer a subtype of all types. Instead, the type hierarchy looks like this: - +Null Safety Hierarchy After Since `Null` is no longer a subtype, no type except the special `Null` class permits the value `null`. We've made all types *non-nullable by default*. If you @@ -202,7 +202,7 @@ problems. We model this by making every nullable type a supertype of its underlying type. You can also safely pass `null` to something expecting a nullable type, so `Null` is also a subtype of every nullable type: - +Nullable But going the other direction and passing a nullable type to something expecting the underlying non-nullable type is unsafe. Code that expects a `String` may @@ -281,7 +281,7 @@ returns. With the removal of implicit downcasts, this becomes a compile error. Where were we? Right, OK, so it's as if we've taken the universe of types in your program and split them into two halves: - +Nullable and Non-Nullable types There is a region of non-nullable types. Those types let you access all of the interesting methods, but can never ever contain `null`. And then there is a @@ -322,7 +322,7 @@ subtype of it. Dart has no *named* top type. If you need a top type, you want `Object?`. Likewise, `Null` is no longer the bottom type. If it was, everything would still be nullable. Instead, we've added a new bottom type named `Never`: - +Top and Bottom In practice, this means: