Development: Improve openapi generated code

[az108]

Summary

Closes #4

Changes

1. Path template generation — Use original OpenAPI paths instead of regex-parsing encodeParam (broke with openapi-generator 7.18.0+)
2. GET methods in service classes — Services always include all HTTP methods as Observables, regardless of httpResource config
3. Model-to-model imports — Added ./ relative path prefix
4. API-to-model imports — Use tsImports with correct kebab-case model filenames
5. Array-of-enum types — Wrap in Array<> when property is an array
6. Void return types — Explicit <void> type parameter on HttpClient calls
7. Duplicate HttpHeaders import — Static import instead of per-operation conditional
8. Const enum objects — Runtime const objects for enum types (TypeScript type/value pattern)
9. Blob response handling — responseType: 'blob' + observe: 'response' for file downloads
10. Array query params — URLSearchParams.append() instead of join(',') for correct wire format
11. Inline model filenames — Underscore-to-hyphen conversion in toKebabCase()
12. Model output folder — model/ instead of models/
13. Configurable GET API style — generator-config.yaml with documented options for all CLI properties
14. Inline resource support — useHttpResource=true + separateResources=false renders httpResource GET functions inline in *-api.ts alongside Observable class methods (one file per tag)
15. Required query params fix — httpResource functions with required query params now use non-optional params: Signal<T> instead of params?: Signal<T> with ?? {} fallback that lost type info

Architecture

Observable service classes are always generated with all HTTP methods. httpResource functions are generated alongside (not instead of) Observable methods when useHttpResource=true. This means:

• Existing consumer code using .subscribe() / firstValueFrom() never breaks
• New code can opt into signal-based httpResource functions for reactive patterns
• No config change will ever remove methods from the service class

Configuration matrix

useHttpResource	separateResources	Result
false	false	One file: Observable class only
true	false	One file: Observable class + inline httpResource functions
true	true	Two files: Observable class (*-api.ts) + httpResource functions (*-resources.ts)
false	true	Same as false/false (no resource files to generate)

Files changed

File	Changes
Angular21Generator.java	Fixes 1, 2, 4, 8, 11, 12, 13, 14, 15 + comprehensive JavaDoc
api-service.mustache	Fixes 2, 4, 6, 7, 9, 10, 13, 14
api-resource.mustache	Fix 4, 15
model.mustache	Fixes 3, 5, 8
generator-config.yaml	Fix 13, 14 (new file)

Test plan

• Build the generator: ./gradlew build
• Run against a sample OpenAPI spec and verify generated output compiles
• Verify model imports use ./ relative paths
• Verify API imports reference ../model/ with correct filenames
• Verify enum types generate both union types and const objects
• Verify blob endpoints use responseType: 'blob'
• Verify with useHttpResource=true, separateResources=true: Observable class in *-api.ts has all methods, *-resources.ts has httpResource GETs
• Verify with useHttpResource=true, separateResources=false: Single file with Observable class + inline httpResource functions
• Verify with useHttpResource=false: Observable class only, no httpResource functions
• Verify GET-only tags still generate a service class (not skipped)
• Verify httpResource functions with required query params use non-optional params: Signal<T>

🤖 Generated with Claude Code