Cursor rule

1---
2description: Objective-C standards and Contentstack iOS SDK layout for CDA sources
3globs:
4  - "Contentstack/**/*.{h,m}"
5  - "ContentstackInternal/**/*.{h,m}"
6  - "ThirdPartyExtension/**/*.{h,m}"
7---
8 
9# iOS SDK Standards – Contentstack iOS CDA SDK
10 
11Apply these conventions when editing Objective-C code in the SDK (not test targets).
12 
13## Language and runtime
14 
15- **Objective-C** with Apple’s modern conventions: use `NS_ASSUME_NONNULL_BEGIN` / `END` (or explicit `nullable` / `nonnull`) on public headers where the project already does.
16- **Swift consumers** import the module; avoid breaking Swift names without good reason (Objective-C names map to Swift automatically).
17 
18## Layout and modules
19 
20- **Public API** lives under **`Contentstack/`** (headers shipped via `public_header_files` in the podspec).
21- **Internal implementation** lives under **`ContentstackInternal/`** (HTTP, URLs, constants, extensions). Do not expose internal headers as public API without an explicit decision.
22- **Vendored / shared code** under **`ThirdPartyExtension/`** (e.g. `CSURLSessionManager`, markdown, ISO8601). Keep changes minimal and consistent with upstream vendoring policy.
23 
24## Naming
25 
26- **Classes:** Prefix or unprefixed names as established in this SDK (`Stack`, `Config`, `CSIOCoreHTTPNetworking`, etc.); do not introduce conflicting generic names.
27- **Methods:** Objective-C style, descriptive selectors; match existing patterns for “fetch”, “callback”, “withConfig:”, etc.
28- **Categories:** Use project prefixes on category methods to avoid collisions (`cs_` or existing project convention).
29- **Test classes:** See **testing.mdc** (`*Test` XCTest case naming).
30 
31## Headers
32 
33- Public declarations belong in **`Contentstack/*.h`**; import umbrella patterns consistent with **`Contentstack.h`**.
34- Use forward declarations (`@class`) in headers when possible to reduce compile coupling.
35 
36## Documentation
37 
38- Public API should retain or extend the existing block-comment style in headers (parameters, return value, Obj-C / Swift snippets where already used).
39 
40## General
41 
42- Prefer explicit error handling over silent failure when adding new async or network paths.
43- Match existing memory management (ARC); avoid introducing non-ARC patterns.
44