<commit_before># TODO

* Support mixins/customizations of generated source code. This currently
  affects S3, DynamoDB in aws-sdk-core, and S3, SNS, SQS, EC2, IAM from
  resources.

* Implement support for resource collection batch actions. Currently, the
  generated methods are non-functional.

* `Aws::S3::Client` had previously modified the API model prior to generating
   API documentation that added an `:accelerate` option to all but three options.
   We are no longer generating docs in a separate pass of the models. Leaving
   these customizations makes them valid request parameters.

   We need to consider how to re-apply these options to documentation.

   * Add them to the model, and remove the values prior to serialization.
     This has the side-effect of making them members in the generated types.

   * Write a documentation plugin to document the option, but not modify
     the api. This becomes extra code to support. We'd like to eliminate
     all docuemntation plugins if possible.<commit_msg>Added more todo items.<commit_after># TODO

* Support mixins/customizations of generated source code. This currently
  affects S3, DynamoDB in aws-sdk-core, and S3, SNS, SQS, EC2, IAM from
  resources.

* Implement support for resource collection batch actions. Currently, the
  generated methods are non-functional.

* `Aws::S3::Client` had previously modified the API model prior to generating
   API documentation that added an `:accelerate` option to all but three options.
   We are no longer generating docs in a separate pass of the models. Leaving
   these customizations makes them valid request parameters.

   We need to consider how to re-apply these options to documentation.

   * Add them to the model, and remove the values prior to serialization.
     This has the side-effect of making them members in the generated types.

   * Write a documentation plugin to document the option, but not modify
     the api. This becomes extra code to support. We'd like to eliminate
     all docuemntation plugins if possible.

* `aws-sdk` gem needs to dynamically list it's dependencies and autoloads,
   they are currently static.

* Need to decide on versioning scheme for service gems. Currently they
  default to 1.0.0. This means `aws-sdk` v2.5.0 will depends on 70+ v1 gems.
  What version should they start at? (I'm leaning towards 1.0)

{'fraction_non_alphanumeric': 0.050168634064080946, 'fraction_numerical': 0.008010118043844857, 'mean_word_length': 3.784274193548387, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2934007', 'n_tokens_mistral': 626, 'n_tokens_neox': 606, 'n_words': 334}