You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user's `ProfileView` includes their `Did`, `Handle`, display name, description, avatar etc. It also includes their follower, following and posts count, information
12
+
on the number of lists, starter packs and feed generators they have created, as well who they will accept direct messages from.
13
+
14
+
The profile view also includes a `Viewer` property which describes the relationship between the user that requested the profile and the user the profile refers to,
15
+
including properties such as `Muted`, when the user requesting the profile has muted the user the profile refers to, as well as `BlockedBy`, `Following`, `FollowedBy`
16
+
and other properties that will effect how you should render the profile, or the item in a view that also contains the author profile, to the requesting user.
17
+
18
+
Feeds, timelines etc. will also contain a `ProfileViewBasic`, `ProfileView` or `ProfileViewDetailed`, depending on the view or API definition.
Bluesky supports a composible verification system where various organications will verify accounts, for example the New York Times may verify their reporters. The
27
+
`Verification` property holds the verification status for a user, and a list of the verifiers who have verified it. The `VerifiedStatus` can be valid, invalid, none or unknown,
28
+
you can use this to decide if you want to display an indicator of the status to your users.
Copy file name to clipboardExpand all lines: docs/docs/sourceGeneration.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,24 +55,23 @@ and passing in the `JsonSerializerOptions.Default` from your code where you have
55
55
56
56
### Annotating your own classes for json source generation
57
57
58
-
The reference `AtProto` implementation is quite laissez faire about where the `$type` property appears in serialized JSON. Make sure that the`AllowOutOfOrderMetadataProperties` is set
59
-
to `true`` in your `JsonSourceGenerationOptions` on your `SourceGenerationContext` class. For example,
58
+
The reference `AtProto` implementation is quite laissez faire about where the `$type` property appears in serialized JSON. Make sure that the
59
+
`AllowOutOfOrderMetadataProperties` is set to `true`` in your `JsonSourceGenerationOptions` on your `SourceGenerationContext` class. For example,
You must also ensure both your record classes (those deriving from `AtProtoRecord`) and your record value classes (those deriving from `AtProtoRecordValue`) are marked as `JsonSerializable` in your
75
-
`JsonSerializerContext`. Additionally you must also add the `AtProtoRecord<YourRecordValue>` class to the context.
73
+
You must also ensure both your record classes (those deriving from `AtProtoRecord`) and your record value classes (those deriving from `AtProtoRecordValue`) are marked
74
+
as `JsonSerializable` in your `JsonSerializerContext`. Additionally you must also add the `AtProtoRecord<YourRecordValue>` class to the context.
76
75
77
76
For example, if you have a custom `AtProtoRecordValue` and corresponding `AtProtoRecord<TRecordValue>` it should look something like the following.
78
77
@@ -93,7 +92,6 @@ For example, if you have a custom `AtProtoRecordValue` and corresponding `AtProt
* Reduced memory usage: Native AOT apps can show reduced memory demands, depending on the work it does.
120
118
121
119
If you wish to use AOT with your own classes you must enable JSON Source Generation for your `AtProtoRecordValue` and `AtProtoRecord` records and follow the guidance above.
120
+
121
+
> [!WARNING]
122
+
> Trimming is not currently supported due to a bug in the [linker](https://github.com/dotnet/runtime/issues/114307).
0 commit comments