fog / fog

69%

master: 97%

LAST BUILD ON BRANCH require_json_in_core

branch: require_json_in_core

CHANGE BRANCH

x

Reset

• require_json_in_core
• 2706_bump_libvirt
• add_2_1_1_to_travis
• add_minitest
• aws_dns_omit_ttl_for_alias_records
• change_version_short_option
• connection_deprecation_warning
• coverage_opt_in
• disable_digital_ocean_test_fail
• edge_gemfile
• extract_archive_bad_require
• extract_mock_env_under_travis
• fix_internet_archive_tag
• fix_joyent_service_declarations
• fog-brightbox_v0.0.1
• improve_vsphere_network_interfaces
• isolate_data_exchange_formats
• master
• rackspace_requires
• rackspace_storage_docs
• reauth
• reduce_ci_burden
• release_notes
• release_v1-22-1
• remove_libvirt_dependency
• remove_remaining_services
• remove_trailing_whitespace
• replace_fog_connection
• test_providers
• use_core_gem
• use_fog_json
• v1.16.0
• v1.17.0
• v1.18.0
• v1.19.0
• v1.20.0
• v1.21.0
• v1.22.1

Build # 3289

Build Type

push

travis-ci

Committed by tokengeek

Commit Message

Require `json` or `xml` in provider cores

Since `fog-json` was extracted from `fog` it means if you rely on:

    require "fog/provider/compute"

`Fog::JSON` was not defined although it was supposed to be a supported
use case.

This adds the requires for JSON or XML based APIs based on a quick scan
of each provider to declare the required part.

AWS seems to be relying on both. Which is nice.

Providers relying on native code dependencies

Run Details

34 of 34 new or added lines in 32 files covered. (100.0%)

45184 of 65223 relevant lines covered (69.28%)

16.31 hits per line