* feat(docs): code samples with ts type stripping
Introduce a new option to `$CodeSample`, `convertToJs`, which takes a
code sample written in TypeScript and strips the types to produce a
JavaScript version.
Adds tests for type stripping.
* Clarify instructions
---------
Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>
We have a global troubleshooting view at /guides/troubleshooting, but
for greater visibility, we should also have product-specific
troubleshooting views. This is the same view and same data as the global
page, but filtered down to a specific product.
* General updates and switch to Svelte 5
* Update code example to Svelte 5
* Update some examples to use codesamples component
* Add Svelte to codesample component
* Final code updates
* Add more CodeSample components
* feat: move storage settings
* feat: redirect
* feat: database settings in service area
* feat: move data api settings
* fix: revert data API placement
* feat: minor UX touches
* fix: simplify configuration group
* feat: references to database settings
* feat: references to storage settings
* fix: redirects and formatting
* fix: Import StorageMenu dynamically to avoid SSR issues with useLocalStorage
* fix: move Data API closer to semantic siblings
* fix: revert smart comma
* Shift bucket sort logic into storage explorer store
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
The original documentation made it sound like the `vt` parameter specified how long until the message became invisible, when in reality it is how long the message is invisible. See: https://github.com/tembo-io/pgmq/tree/main?tab=readme-ov-file#read-messages
> Read 2 message from the queue. Make them invisible for 30 seconds. If the messages are not deleted or archived within 30 seconds, they will become visible again and can be read by another consumer.
* docs: clarify requirement for combining restrictive policy with permissive policy
Adding a note like this would have saved me hours, explaining that a single 'restrictive' RLS policy alone will fail unless combined with another policy that returns true, ensuring the combined OR condition is satisfied. This clarifies the need for at least one policy to explicitly grant access when multiple RLS policies are in place.
* Update apps/docs/content/guides/auth/auth-anonymous.mdx
---------
Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
This adds myself to the humans.txt file
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Adds a single line with my name to humans.txt
What is the current behavior?
I am not on the list :(
What is the new behavior?
I am on the list :)
The argument, I previously fixed, was actually correct for version @2 but the header said to use @1, so better change that and use the newer argument style.
