Commit Graph
6 Commits
Author SHA1 Message Date
Guilherme Souza 4f3863264d feat(docs): add typeSpec entries for Swift properties
Properties carrying @category are now stored in typeSpec.methods with
empty params and ret holding the property type. This matches how methods
are stored and lets the renderer display description + type for Swift
properties. JavaScript properties are unaffected since they never carry
@category in their TypeDoc output.
2026-06-24 21:48:07 -03:00
Guilherme Souza b82fa2da3d chore(docs): regenerate Swift TypeDoc spec with correct param and return types
Rebuilt with updated transform.ts that strips argument labels from parameter
declaration fragments (e.g. UUID instead of uid: UUID) and emits intrinsic
rather than reference for simple Swift type names (so return types render
correctly in ReturnTypeDetails instead of being skipped as nameOnly).
2026-06-24 15:03:11 -03:00
Guilherme Souza 55a6131a67 chore(test): update swift spec.json with variant fix (866 function slugs, 6 categories) 2026-06-24 13:49:03 -03:00
Guilherme Souza 3d6fc67474 chore(test): add swift TypeDoc JSON from CI artifact for e2e testing
Generated from supabase/supabase-swift#1034 workflow run 28107689217.
This file is normally gitignored and downloaded at build time via the
Makefile download.swift.v2 target once GitHub Pages is enabled.
Force-added here only to unblock e2e pipeline testing.
2026-06-24 12:04:50 -03:00
Guilherme Souza 25081de61a feat(docs): migrate Swift v2 reference to TypeDoc pipeline
Wire supabase-swift into the new reference content pipeline
(build-reference-content.ts), matching how javascript-v2 works.

- Add spec/reference/swift/v2/config.json with category order and
  navigation prefix config (Authentication, Database, Edge Functions,
  Realtime, Storage, Client)
- Add introduction.mdx and installing.mdx partials
- Add download.swift.v2 Makefile target that fetches the TypeDoc JSON
  from supabase.github.io/supabase-swift/v2/spec.json
- Add 'swift-v2' to SUPPORTS_NEW_REFERENCE_PROCESS so the Next.js
  router reads from the new pipeline output instead of the legacy
  generated/ YAML files

The TypeDoc JSON is generated by supabase/supabase-swift's
generate-swift-docs.yml workflow using the swift-docs tool from
supabase/sdk.
2026-06-23 11:03:34 -03:00
f20cd22dc3 docs: improve SDK automation build step on docs (#46163)
# Second try of making a new better process for SDK automation

Instead of building a new pipeline. We will take the lessons learned
form round 1, plus the good design and improvement on DX quality for
drop-in file as a single step required from SDK team and produce almost
identical set of files as used right now to render using the current
pipeline.



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* New reference-content pipeline producing per-library reference
artifacts and integrating into prebuilds, search ingestion, and
rendering (type-aware examples).

* **Documentation**
* Added comprehensive JavaScript SDK v2 reference content and partials
(Auth MFA, passkeys, admin, TypeScript support, filters, modifiers,
Installing, Initializing, Buckets, etc.).

* **Tests & CI**
* Added regression snapshot test and updated workflows to refresh
reference snapshots and ensure spec downloads.

* **Chores**
* Updated ignore rules, build scripts, Makefile targets, and package
lifecycle hooks.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Katerina Skroumpelou <mandarini@users.noreply.github.com>
Co-authored-by: Katerina Skroumpelou <sk.katherine@gmail.com>
2026-06-03 11:46:02 +03:00