Commit Graph

19 Commits

Author SHA1 Message Date
0368c27c2c
move to state parameter and index level rather than prefix
This also includes a small change to force output of mappings even if empty
New zig correctly detects that without any field, we end up trying to use
a constant that does not exist (this is in the generated code)
2021-09-05 13:09:22 -07:00
7f178bcc91
provide ability to handle requests built at runtime
Some checks failed
continuous-integration/drone/push Build is failing
This commit adds a new interface that is capable of runtime
use. By calling Request(action).call(request, options), the request
object can now be built at runtime. This change also moves the client
object into the options structure. It also moves the metaInfo generated
function to a type-based function rather than requiring an instance for
binding.
2021-08-24 17:02:28 -07:00
8e853e9a82
rest json v1 basic requests (responses tbd)
All checks were successful
continuous-integration/drone/push Build is passing
This provides initial implementation with some basic calls
working. Only GET requests have been verified so far.
Http header support missing. POST/PUT might work, but
have not been tested. Currently the demo tests are
failing due to a response deserialization issue that
is still being debugged
2021-08-13 18:12:05 -07:00
6f53ed6dcf
http trait necessary for rest json support
All checks were successful
continuous-integration/drone/push Build is passing
2021-08-13 11:03:11 -07:00
17b0ae9551
provide smithy-based json serialization for request data
All checks were successful
continuous-integration/drone/push Build is passing
This will use the actual structure name or the override
from the trait as needed. Return value support
is also enabled in the code generation but not in
aws.zig. The current fuzzy checks should get most
of the way there though
2021-08-13 10:28:29 -07:00
f21ce40186
include proper service name and use it 2021-08-12 17:51:07 -07:00
00b2ab3d27
initial support for json 1.0 2021-08-12 14:24:24 -07:00
c7bff8a5e7
correct remaining to_snake issues in service manifest 2021-07-23 14:04:12 -07:00
dfa0be60b9
update code generation without containing struct
Some checks failed
continuous-integration/drone/push Build is failing
Instead we will rely here on the implicit struct provided by the file
itself. This means that when the service_manifest.zig import is
assigned, we don't end up with a construct like "manifest.sts.sts" to
get to the sts service. This simplifies greatly the way that
servicemodel.zig needs to behave.

One down side, however, is that the structure does not seem
accessible with the current zig language, making metaInfo unable
to access itself as it did before. Or maybe it can, I just can't find
it. So, this change also adds a new "service_metadata" public constant
with the same declarations being published at the file level, and
that is the new return from the metaInfo function. Our aws.zig
only really needs the action and that metadata, so we're ok with that
even if there is some duplication (we could codegen pointers over, and
maybe should to save a little bit of space).
2021-06-30 13:40:20 -07:00
de41b456d3
address unused variable in generated metaInfo function 2021-06-30 09:12:34 -07:00
267e72051d
make services direct imports/pub const in generated service manifest 2021-06-30 09:11:53 -07:00
9c3be78d9f
address new compilation errors introduced in zig cf65ab8 2021-06-30 09:10:08 -07:00
ad7aa96678
use new smithy package in generated code 2021-06-30 09:07:35 -07:00
ac07c9300f
extract smithy to separate package 2021-06-30 09:05:21 -07:00
22e39dd6e1
allow for spaces in the name to be "handled" (ignored) 2021-06-29 17:19:34 -07:00
aa5b46c046
move codegen out of src - we will handle differently 2021-06-29 17:10:01 -07:00
c2710be165
move codegen under src/ 2021-06-03 17:35:14 -07:00
f997907bf1
add traits everywhere/make "required" fixes/add ec2_query_name/json_name 2021-05-29 21:04:35 -07:00
f068dce413
codegen all the things 2021-05-29 18:17:45 -07:00