TJ
TJ
Looks pretty good to me, I think the only tricky part is say for example you have a nested object passed to a call which should _not_ be camel-cased. In...
At the moment it allows arbitrary objects: ```json { "name": "fields", "description": "the log fields.", "type": "object" }, ``` Which I'm using for user-defined event fields. I didn't think about...
Snake-case doesn't bother me here but if we're solving for timestamps anyway we might as well. I still kind of like plain objects over using Maps personally, more just from...
The generated approach is what I did with validation in the Go server portion and it works pretty nicely https://github.com/apex/rpc/blob/master/generators/gotypes/gotypes.go#L155-L168. The schemas can get pretty huge so I don't think...
somehow I missed that haha, yeah I think we should use whatever is idiomatic for the target language, so SGTM, I'll fix that today
370c365 thanks!
oh actually I just remembered why it's this way, because TS will serialize the fields incorrectly. If fields are defined as `project_id` in the schema, then you get `projectId` since...
It's definitely doable to recurse, but I'm not sure it's really worth the pain, I don't mind the snake-case much personally but I don't use any linters. If there is...
I forgot to document this option: https://github.com/tj/staticgen/blob/master/config.go#L28 that should do the trick, at least for 404
Hmm I'll try to check it out soon, config looks fine to me