truemail-client 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 8d21444ecc6092bd4689dd696c33b2af42b142f3d2656a2616b1f6d538acbb00
4
+ data.tar.gz: 6c81b075c1709daa53b17c18b8439882ca110083aa788e59a9f04ff66dd2b89f
5
+ SHA512:
6
+ metadata.gz: f557bb644b31fcc18b66c2159ab7fd507d70a40dd28f3000a3580b57d82887dfdd69bb776191c927ba886e5258bbe41af31549ca0a735d6adfc2b34774ee147e
7
+ data.tar.gz: d34a0a74c8b010d243605b85b3498de7954981a4d132f92d399261ee54e57d1f8ff2caa98200a7eb679c8b51b382737f15cb8b9edf585c5f2d874ec92df4f5f7
@@ -0,0 +1,89 @@
1
+ defaults: &defaults
2
+ working_directory: ~/truemail-ruby-client
3
+ docker:
4
+ - image: circleci/ruby:2.5.0-node
5
+ environment:
6
+ CC_TEST_REPORTER_ID: 183d1173cc05e4e5dbd07ddb60a04b9c4115ed11a4bacda0e1834572eb168c51
7
+
8
+ references:
9
+ restore_bundle_cache: &restore_bundle_cache
10
+ restore_cache:
11
+ keys:
12
+ - truemail-ruby-client-{{ checksum "truemail-client.gemspec" }}
13
+
14
+ bundle_install: &bundle_install
15
+ run:
16
+ name: Installing gems
17
+ command: bundle install --path vendor/bundle
18
+
19
+ save_bundle_cache: &save_bundle_cache
20
+ save_cache:
21
+ key: truemail-ruby-client-{{ checksum "truemail-client.gemspec" }}
22
+ paths:
23
+ - vendor/bundle
24
+
25
+ install_codeclimate_reporter: &install_codeclimate_reporter
26
+ run:
27
+ name: Install Code Climate Test Reporter
28
+ command: |
29
+ curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter
30
+ chmod +x ./cc-test-reporter
31
+
32
+ version: 2
33
+ jobs:
34
+ linters:
35
+ <<: *defaults
36
+
37
+ steps:
38
+ - checkout
39
+
40
+ - <<: *restore_bundle_cache
41
+ - <<: *bundle_install
42
+ - <<: *save_bundle_cache
43
+
44
+ - run:
45
+ name: Running overcommit
46
+ command: |
47
+ bundle exec overcommit -s
48
+ SKIP=AuthorEmail,AuthorName bundle exec overcommit -r
49
+
50
+ tests:
51
+ <<: *defaults
52
+
53
+ steps:
54
+ - checkout
55
+
56
+ - <<: *restore_bundle_cache
57
+ - <<: *bundle_install
58
+ - <<: *save_bundle_cache
59
+ - <<: *install_codeclimate_reporter
60
+
61
+ - run:
62
+ name: Running tests
63
+ command: |
64
+ mkdir /tmp/test-results
65
+ ./cc-test-reporter before-build
66
+ bundle exec rspec
67
+
68
+ - run:
69
+ name: Code Climate Test Coverage
70
+ command: |
71
+ ./cc-test-reporter format-coverage -t simplecov -o "coverage/codeclimate.$CIRCLE_NODE_INDEX.json"
72
+
73
+ - store_test_results:
74
+ path: /tmp/test-results
75
+
76
+ - store_artifacts:
77
+ path: /tmp/test-results
78
+ destination: test-results
79
+
80
+ - deploy:
81
+ command: |
82
+ ./cc-test-reporter sum-coverage --output - --parts $CIRCLE_NODE_TOTAL coverage/codeclimate.*.json | ./cc-test-reporter upload-coverage --debug --input -
83
+
84
+ workflows:
85
+ version: 2
86
+ build:
87
+ jobs:
88
+ - linters
89
+ - tests
@@ -0,0 +1,13 @@
1
+ checks:
2
+ argument-count:
3
+ enabled: false
4
+ method-complexity:
5
+ enabled: false
6
+
7
+ plugins:
8
+ rubocop:
9
+ enabled: true
10
+ channel: rubocop-0-76
11
+
12
+ reek:
13
+ enabled: true
@@ -0,0 +1,17 @@
1
+ <!-- Thanks for helping to make Truemail better! Before submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->
2
+
3
+ ### New Issue Checklist
4
+
5
+ - [ ] I have updated truemail-ruby-client to the latest version
6
+ - [ ] I have read the [Contribution Guidelines](https://github.com/truemail-rb/truemail-ruby-client/blob/master/CONTRIBUTING.md)
7
+ - [ ] I have read the [documentation](https://github.com/truemail-rb/truemail-ruby-client/blob/master/README.md)
8
+ - [ ] I have searched for [existing GitHub issues](https://github.com/truemail-rb/truemail-ruby-client/issues)
9
+
10
+ ### Issue Description
11
+ <!-- Please include what's happening, expected behavior, and any relevant code samples -->
12
+
13
+ ##### Complete output when running truemail, including the stack trace and command used
14
+
15
+ <details>
16
+ <pre>[INSERT OUTPUT HERE]</pre>
17
+ </details>
@@ -0,0 +1,46 @@
1
+ # PR Details
2
+
3
+ <!-- Provide a general summary of your changes in the Title above -->
4
+
5
+ ## Description
6
+
7
+ <!--- Describe your changes in detail -->
8
+
9
+ ## Related Issue
10
+
11
+ <!--- This project only accepts pull requests related to open issues -->
12
+ <!--- If suggesting a new feature or change, please discuss it in an issue first -->
13
+ <!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
14
+ <!--- Please link to the issue here: -->
15
+
16
+ ## Motivation and Context
17
+
18
+ <!--- Why is this change required? What problem does it solve? -->
19
+
20
+ ## How Has This Been Tested
21
+
22
+ <!--- Please describe in detail how you tested your changes. -->
23
+ <!--- Include details of your testing environment, and the tests you ran to -->
24
+ <!--- see how your change affects other areas of the code, etc. -->
25
+
26
+ ## Types of changes
27
+
28
+ <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
29
+
30
+ - [ ] Docs change / refactoring / dependency upgrade
31
+ - [ ] Bug fix (non-breaking change which fixes an issue)
32
+ - [ ] New feature (non-breaking change which adds functionality)
33
+ - [ ] Breaking change (fix or feature that would cause existing functionality to change)
34
+
35
+ ## Checklist
36
+
37
+ <!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
38
+ <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
39
+
40
+ - [ ] My code follows the code style of this project
41
+ - [ ] My change requires a change to the documentation
42
+ - [ ] I have updated the documentation accordingly
43
+ - [ ] I have read the [**CONTRIBUTING** document](https://github.com/truemail-rb/truemail-ruby-client/blob/master/CONTRIBUTING.md)
44
+ - [ ] I have added tests to cover my changes
45
+ - [ ] I have run `bundle exec rspec` from the root directory to see all new and existing tests pass
46
+ - [ ] I have run `rubocop` and `reek` to ensure the code style is valid
@@ -0,0 +1,9 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /_yardoc/
4
+ /coverage/
5
+ /doc/
6
+ /pkg/
7
+ /spec/reports/
8
+ /tmp/
9
+ .rspec_status
@@ -0,0 +1,32 @@
1
+ PreCommit:
2
+ AuthorEmail:
3
+ enabled: true
4
+ required: false
5
+
6
+ AuthorName:
7
+ enabled: false
8
+
9
+ BundleAudit:
10
+ enabled: true
11
+
12
+ Fasterer:
13
+ enabled: true
14
+ include: '**/*.rb'
15
+
16
+ TrailingWhitespace:
17
+ enabled: true
18
+
19
+ RuboCop:
20
+ enabled: true
21
+ flags: ['--format=emacs', '--force-exclusion', '--display-cop-names']
22
+
23
+ Reek:
24
+ enabled: true
25
+ flags: ['--force-exclusion']
26
+
27
+ PostCheckout:
28
+ ALL:
29
+ quiet: true
30
+
31
+ IndexTags:
32
+ enabled: true
@@ -0,0 +1,21 @@
1
+ detectors:
2
+ IrresponsibleModule:
3
+ enabled: false
4
+
5
+ LongParameterList:
6
+ enabled: false
7
+
8
+ TooManyStatements:
9
+ enabled: false
10
+
11
+ Attribute:
12
+ exclude:
13
+ - Truemail::Client::Configuration#secure_connection
14
+
15
+ ControlParameter:
16
+ exclude:
17
+ - Truemail::Client#raise_unless
18
+ - Truemail::Client::Configuration#raise_unless
19
+
20
+ exclude_paths:
21
+ - spec/support/helpers
data/.rspec ADDED
@@ -0,0 +1,2 @@
1
+ --require spec_helper
2
+ --format documentation
@@ -0,0 +1,108 @@
1
+ require:
2
+ - rubocop-rspec
3
+ - rubocop-performance
4
+
5
+ AllCops:
6
+ DisplayCopNames: true
7
+ DisplayStyleGuide: true
8
+ TargetRubyVersion: 2.5
9
+
10
+ Metrics/ClassLength:
11
+ Max: 150
12
+
13
+ Metrics/MethodLength:
14
+ Max: 15
15
+
16
+ Metrics/BlockLength:
17
+ Enabled: false
18
+
19
+ Metrics/CyclomaticComplexity:
20
+ Enabled: false
21
+
22
+ Metrics/PerceivedComplexity:
23
+ Enabled: false
24
+
25
+ Naming/VariableNumber:
26
+ Enabled: false
27
+
28
+ Naming/RescuedExceptionsVariableName:
29
+ Enabled: false
30
+
31
+ Style/Documentation:
32
+ Enabled: false
33
+
34
+ Style/DoubleNegation:
35
+ Enabled: false
36
+
37
+ Style/EmptyCaseCondition:
38
+ Enabled: false
39
+
40
+ Style/ParallelAssignment:
41
+ Enabled: false
42
+
43
+ Style/RescueStandardError:
44
+ Enabled: false
45
+
46
+ Style/HashEachMethods:
47
+ Enabled: false
48
+
49
+ Style/HashTransformKeys:
50
+ Enabled: false
51
+
52
+ Style/HashTransformValues:
53
+ Enabled: false
54
+
55
+ Layout/LineLength:
56
+ Max: 140
57
+
58
+ Layout/ClassStructure:
59
+ Enabled: true
60
+ Categories:
61
+ module_inclusion:
62
+ - include
63
+ - prepend
64
+ - extend
65
+ associations:
66
+ - has_one
67
+ - has_many
68
+ - belongs_to
69
+ - has_and_belongs_to_many
70
+ ExpectedOrder:
71
+ - module_inclusion
72
+ - constants
73
+ - associations
74
+ - public_class_methods
75
+ - initializer
76
+ - public_methods
77
+ - protected_methods
78
+ - private_methods
79
+
80
+ Layout/EmptyLineAfterGuardClause:
81
+ Enabled: false
82
+
83
+ Lint/NonDeterministicRequireOrder:
84
+ Enabled: false
85
+
86
+ RSpec/ExampleLength:
87
+ Enabled: false
88
+
89
+ RSpec/NestedGroups:
90
+ Enabled: false
91
+
92
+ RSpec/MultipleExpectations:
93
+ Enabled: false
94
+
95
+ RSpec/MessageChain:
96
+ Enabled: false
97
+
98
+ RSpec/ContextWording:
99
+ Enabled: false
100
+
101
+ RSpec/AnyInstance:
102
+ Enabled: false
103
+
104
+ RSpec/MessageSpies:
105
+ Enabled: false
106
+
107
+ RSpec/MultipleDescribes:
108
+ Enabled: false
@@ -0,0 +1 @@
1
+ truemail-client
@@ -0,0 +1 @@
1
+ ruby-2.5.0
@@ -0,0 +1,6 @@
1
+ # Changelog
2
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
3
+
4
+ ## [0.1.0] - 2020-03-00
5
+ ### First release
6
+ - implemented first version of Truemail Ruby client
@@ -0,0 +1,74 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at admin@bestweb.com.ua. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [http://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: http://contributor-covenant.org
74
+ [version]: http://contributor-covenant.org/version/1/4/