authenticated requests with js-sdk

[c-nv-s]

I have a question about https://pocketpages.dev/docs/plugins/js-sdk#example-working-with-collections

<script server>

// Get an anonymous client
// const client = pb()

 // Get an authenticated client for the current request
  const client = pb({ request })

  // Create a record
  const post = client.collection('posts').create({
    title: 'Hello World',
    content: 'My first post',
  })
  
  </script>

the docs say that we are getting an authenticated client for the request... assuming the subsequent request would be authenticated as the current user?

To me that still suggests that if I have API rules set on collections they will still be respected. i.e.
if on the posts collection I have the create rule @request.auth.id != "" then the above request would qualify?

this doesn't seem to work and it seems that only if I remove the API rule will the request work.
Is there something I am overlooking or how can someone keep the auth context with request?

[benallfree]

It's possible the example is bad. Have you looked at https://github.com/benallfree/pocketpages/blob/main/packages/plugins/js-sdk/src/index.ts#L44 ?

[c-nv-s]

@benallfree In trying to debug my issue I've upgraded to the latest because I think that's where my issue lay.
However in doing so (using the auth starter) I've noticed that if you try to run pocketbase on any other port number besides the default 8090 (e.g. pocketbase serve --http 127.0.0.1:9000 --dev) then you can't access the auth login/out pages, suggesting to me something is hardcoded somewhere :-(
I vaguely remember raising something like this with you before.

[benallfree]

Are you talking about https://github.com/benallfree/pocketpages/blob/main/packages/plugins/js-sdk/src/index.ts#L43

[c-nv-s]

the original issue of this discussion is fixed by upgrading to a recent version of pocketpages... I didn't check my old version number but I believe anything above https://github.com/benallfree/pocketpages/releases/tag/pocketpages%400.20.0 should be fine and then the API rules are for the collection are now being respected.