[request]: Add a link to the return type in the fluent client docs

[rcoh]

Tell us about your request

Add a link to the return type to the fluent builder method in the docs. Currently docs like: https://docs.rs/aws-sdk-s3/latest/aws_sdk_s3/client/struct.Client.html#method.list_buckets don't link to the return type—customers need to click through to find the send method to figure out the actual return type.

Tell us about the problem you're trying to solve.

Use the SDK

Are you currently working around this issue?

IDE type hints, clicking through to the send method.

Additional context

filed on behalf of @carllerche

[rcoh]

possible POC: https://gist.github.com/carllerche/2edccd415957aed257c878fef9e03f25

[zamazan4ik]

I am not sure, it is a related issue or not.

E.g. in this piece of documentation some links are not working (consider "(using UpdateGameServer )" and many others).

I guess it should be linked to something: related Rust primitive or to the corresponding AWS documentation, idk.

[rcoh]

oh great catch! Do you mind filing a separate issue? We'll track that and down and get it fixed.

…

On Sat, Dec 18, 2021 at 8:40 PM Alexander Zaitsev ***@***.***> wrote: I am not sure, it is a related issue or not. E.g. in this piece of documentation <https://docs.rs/aws-sdk-gamelift/latest/aws_sdk_gamelift/client/fluent_builders/struct.ClaimGameServer.html> some links are not working (consider "(using UpdateGameServer )" and many others). I guess it should be linked to something: related Rust primitive or to the corresponding AWS documentation, idk. — Reply to this email directly, view it on GitHub <#348 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADYKZ5G7UZCRWYYI5L4B5LURUZ2DANCNFSM5KHARZKA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[zamazan4ik]

Sure, no problem. I will create a separate issue.

[zamazan4ik]

New issue is here: #357

[Velfi]

landed in v0.5.2

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.