Commit Graph

43 Commits

Author SHA1 Message Date
7d80f42a3e
update to zig 0.13-dev.365 (zig nominated build 2024.05)
Some checks failed
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Failing after 1m57s
aws-zig nightly build / build-zig-nightly (push) Failing after 3m49s
2024-06-04 14:53:09 -07:00
99a61c0bd2
update aws-zig to zig 0.12.0 (example will still fail)
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 2m25s
2024-04-22 08:23:01 -07:00
d442671275
upgrade zig build gen build command to zig 0.12
This removes the copied Package.zig as we can now use the actual package
manager and look at our available dependencies in build.zig. This may
break again later as I believe lazy dependencies are planned, which will
have us search for a solution to tell the build system we're expecting
this dependency.
2024-03-30 15:26:24 -07:00
79d73cf09f
support for enum, document, and...dear lord...unit 2024-02-29 13:53:32 -08:00
3a027b6cd9
codegen support for more reserved words 2024-02-29 13:49:57 -08:00
69d8151ac8
make sigv4_name and arn_namespace optional 2024-02-29 13:49:21 -08:00
2db4188dbc
more logging to help codegen debug 2024-02-29 13:46:58 -08:00
melhindi
7a5fa0bb2e Replace var with const where applicable
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m37s
2024-01-18 13:43:45 +01:00
e8bfd0af6d
codegen: clean up generated file names
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 8m22s
2023-09-06 12:11:12 -07:00
fb36dc83d5
skip processing if all hashes match
All checks were successful
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Successful in 7m8s
2023-08-25 17:20:51 -07:00
a58a2cba41
adjustments in prep for hash optimization 2023-08-25 15:34:52 -07:00
bad00517a3
create path if it does not exist
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 2m34s
2023-08-15 07:38:57 -07:00
c3da8c067f
only close if opened
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 1m33s
2023-08-15 07:26:14 -07:00
4dacca2d46
introduce verbosity 2023-08-14 22:56:19 -07:00
3b249d62b9
better codegen but without caching
Some checks failed
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 2m4s
2023-08-14 22:38:37 -07:00
5ee53a493d
some codegen changes needed/investigation into http_query (see note)
This fixes main compile issues. Problems that remain:

* json is borked for objects with key/value keys that need to be coerced
* currently all request structures need an http_query declaration, and this may be a hard requirement
* need to revisit all the places where we are reading http response bodies
* there are 35 compile errors that do not have reference traces and will take a while to track down
2023-08-05 12:41:04 -07:00
cfdf4a3141
these are old changes, but I believe part of 0.11 from a while back 2023-08-04 10:06:54 -07:00
803581f647
add http_payload type declaration based on smithy model 2022-05-28 18:00:38 -07:00
611849bde6
add codegen exception for cloudfront/adjust iot sitewise 2022-05-28 17:59:22 -07:00
f374df3fa1
update generated models for xml mappings 2022-02-10 15:13:44 -08:00
1c41737202
upgrade to zig 0.9.0
All checks were successful
continuous-integration/drone/push Build is passing
2022-01-03 08:06:14 -08:00
86b8815051
resolve most recursive type warnings in generator (ssm still has 2)
All checks were successful
continuous-integration/drone/push Build is passing
2021-09-06 15:43:14 -07:00
c6b3f8d6e1
adjust whitespace on generated code 2021-09-05 14:32:20 -07:00
80a76b0998
add jsonStringify implementation 2021-09-05 14:31:38 -07:00
f612b3798a
include std and serializeMap from json.zig in generated code 2021-09-05 13:10:48 -07:00
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
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