Skip to content

Updates to .Net docs, generating a self-host token and .complete() note #185

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.

Sign up for GitHub

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

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Updates to .Net docs, generating a self-host token and .complete() note #185

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
c182999
Updated .NET demo app examples to include new WPF To-Do List demo and…
dean-journeyapps Jun 2, 2025
b79622f
Updated .Net to include all demo projects
dean-journeyapps Jun 11, 2025
55dc51d
Added .complete() note to writing-client-changes recommendations
dean-journeyapps Jun 11, 2025
db2ef5f
Added comment to JWKS_URL indicating its not applicable for Supabase
dean-journeyapps Jun 11, 2025
e9d48a2
Added link on "JOINS" to redirect to parameter query restrictions
dean-journeyapps Jun 11, 2025
2fe16f6
Merge branch 'main' into main
dean-journeyapps Jun 11, 2025
85eede9
Added jwks_uri not applicable when using Supabase
dean-journeyapps Jun 12, 2025
05d36a1
Merge branch 'powersync-ja:main' into main
dean-journeyapps Jun 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions client-sdk-references/dotnet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,9 @@ import DotNetInstallation from '/snippets/dotnet/installation.mdx';
A full API Reference for this SDK is not yet available. This is planned for a future release.
</Card>

<Card title="Example App" icon="code" href="https://github.com/powersync-ja/powersync-dotnet/tree/main/demos/CommandLine">
A small CLI app showcasing bidirectional sync.
</Card>
<Card title="Example Projects" icon="code" href="/resources/demo-apps-example-projects#net-alpha">
Gallery of example projects/demo apps built with .NET and PowerSync.
</Card>
</CardGroup>

<Warning>
Expand Down
4 changes: 4 additions & 0 deletions installation/app-backend-setup/writing-client-changes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,10 @@ We do however recommend the following:
1. Including the error details in the `2xx` response.
2. Writing the error(s) into a separate table/collection that is synced to the client, so that the client/user can handle the error(s).

<Note>
If you don't call `.complete()` on an operation, it will remain in the queue and continue to be retried. This may be intentional to maintain consistency with your remote database, but be aware that incomplete operations will prevent the queue from progressing past that point.
</Note>

For details on approaches, see:

<CardGroup>
Expand Down
2 changes: 1 addition & 1 deletion self-hosting/installation/powersync-service-setup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ client_auth:
# supabase_jwt_secret: your-secret

# JWKS URIs can be specified here.
jwks_uri: http://demo-backend:6060/api/auth/keys
jwks_uri: http://demo-backend:6060/api/auth/keys # Not applicable for Supabase

# JWKS audience
audience: ['powersync-dev', 'powersync']
Expand Down
2 changes: 1 addition & 1 deletion tutorials/self-host/generate-dev-token.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Development tokens can be generated via either
# Client (application end user) authentication settings
client_auth:
# JWKS URIs can be specified here
jwks_uri: !env PS_JWKS_URL
jwks_uri: !env PS_JWKS_URL # Not applicable for Supabase
Copy link
Collaborator

@benitav benitav Jun 11, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might also be good to add this to the main config skeleton https://docs.powersync.com/self-hosting/installation/powersync-service-setup#powersync-configuration and/or demo config which we also share from that main docs page https://github.com/powersync-ja/self-host-demo/blob/main/config/powersync.yaml, assuming this was added because users get confused by it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, will do. Thank you!

jwks:
keys:
- kty: 'oct'
Expand Down
2 changes: 1 addition & 1 deletion usage/sync-rules/guide-many-to-many-and-join-tables.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ JOIN posts ON posts.id = comments.post_id
WHERE board_id = bucket.board_id
```

Unfortunately, joins are not supported in PowerSync's Sync Rules. Instead, we denormalize the data to add a direct foreign key relationship between comments and boards: (Postgres example)
Unfortunately, [JOINS](/usage/sync-rules/parameter-queries#restrictions) are not supported in PowerSync's Sync Rules. Instead, we denormalize the data to add a direct foreign key relationship between comments and boards: (Postgres example)

```sql
ALTER TABLE comments ADD COLUMN board_id uuid;
Expand Down