+2
src/queries/get-invites-from-constellation.ts
+2
src/queries/get-invites-from-constellation.ts
+17
src/lib/utils/arrays.ts
+17
src/lib/utils/arrays.ts
···
+2
src/queries/hooks/useConstellationInvitesQuery.ts
+2
src/queries/hooks/useConstellationInvitesQuery.ts
···+// TODO: use prism instead, so that we can get the backlink, the invite, and the channel's actual record
+21
src/queries/get-invite-from-pds.ts
+21
src/queries/get-invite-from-pds.ts
···+import type { SystemsGmstnDevelopmentChannelInvite } from "@/lib/types/lexicon/systems.gmstn.development.channel.invite";+import { systemsGmstnDevelopmentChannelInviteRecordSchema } from "@/lib/types/lexicon/systems.gmstn.development.channel.invite";
+30
src/queries/hooks/useInviteQuery.ts
+30
src/queries/hooks/useInviteQuery.ts
···
+1
src/providers/authed/MembershipsProvider.tsx
+1
src/providers/authed/MembershipsProvider.tsx
+15
-15
src/queries/initiate-handshake-to.ts
+15
-15
src/queries/initiate-handshake-to.ts
···-error: `Cannot initiate handshake to a lattice at localhost. Provided handshake target's DID was ${did}`,+// error: `Cannot initiate handshake to a lattice at localhost. Provided handshake target's DID was ${did}`,
+67
-1
src/lib/utils/atproto/index.ts
+67
-1
src/lib/utils/atproto/index.ts
···-import { comAtprotoRepoGetRecordResponseSchema } from "@/lib/types/lexicon/com.atproto.repo.getRecord";···+// @ts-expect-error yes, we are coercing something that is explicitly not a string into a string, but in this case we want to be specific. only serviceEndpoints with valid atproto pds URLs should be allowed.+`${pdsEndpointUrl}/xrpc/com.atproto.repo.getRecord?repo=${didDocResult.data.id}&collection=${collection}&rkey=${rKey}`,
+1
-1
assets/oauth-client-metadata.json
+1
-1
assets/oauth-client-metadata.json
+3
-1
package.json
+3
-1
package.json
···
+7
-5
src/components/Chat/index.tsx
+7
-5
src/components/Chat/index.tsx
······
+17
-9
src/lib/hooks/useChannel.ts
+17
-9
src/lib/hooks/useChannel.ts
···"Session info did not resolve to a valid websocket connection. This should not happen and is likely a bug. Check the sessions map object.",···"Session info did not resolve to a valid websocket connection. This should not happen and is likely a bug. Check the sessions map object.",
+1
-3
src/providers/authed/SessionsProvider.tsx
+1
-3
src/providers/authed/SessionsProvider.tsx
···
+1
-1
src/lib/utils/gmstn.ts
+1
-1
src/lib/utils/gmstn.ts
···
+1
-1
src/lib/utils/atproto/oauth.web.ts
+1
-1
src/lib/utils/atproto/oauth.web.ts
···
+4
-6
src/components/Invites/index.tsx
+4
-6
src/components/Invites/index.tsx
······
+82
-23
src/components/Auth/Login.web.tsx
+82
-23
src/components/Auth/Login.web.tsx
······