faithteams-api 2.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 5cc2b7c415987619e7ebcc699f37790daeb0c7c730904c6a42fd6433a7fe72cb
+  data.tar.gz: 2cb6331d07e910eeb623c5274f6e3737a335a0be39c6c1c1a68efb2badada2fe
+SHA512:
+  metadata.gz: 057231fb75f6b1f0bb493698abbd877fbf137c38b8ed43dbbf746ef7a7d04e477fbfd615b09aa3d3d4915ebd70cc4f51817c1849f6e93385a9c1809660eb6936
+  data.tar.gz: 5b18767dbed31ac0d292c29819834fa7e367ee242243487c992e6c3f32be1da7a9956a8eb660cddc1b7586747c3eab9ccfc1f6c5b91ffb066c7df6fcf15ce395

data/.editorconfig

@@ -0,0 +1,11 @@
+[*]
+end_of_line = lf
+trim_trailing_whitespace = true
+insert_final_newline = true
+indent_style = space
+indent_size = 2
+charset = utf-8
+
+[*.{json,md}]
+indent_style = space
+indent_size = 4

data/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @tithely/integrations

data/.github/CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Introduction
+
+First off, thank you for considering contributing to Tithely open source. We strive to be the best platform for developers to build tools for the church and want to thank you for your bug report or pull requests.
+
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
+
+## What We Look For
+
+We welcome any bug reports and documentation corrections or additions. If you have a fix or a bit of functionality you would like to see introduced, please follow our guidelines for submitting a PR. We will work with you to determine if we can incorporate your work right now or plan for it in the future.
+
+# Ground Rules
+
+* We respect all members and welcome diverse viewpoints and contributions. For more information, check out our [Code of Conduct](https://github.com/tithely/tithely-transaction-gem/blob/master/CODE_OF_CONDUCT.md).
+* Keep pull requests as short and direct as possible.
+* Tests must accompany any pull request to show additional or changed behavior.
+
+# Reporting a Bug
+
+If you find a security vulnerability, do NOT open an issue. Email integrations@tithe.ly instead.
+
+For any other bug report, please open an issue [here](https://github.com/tithely/tithely-transaction-gem/issues/new?assignees=&labels=fix&template=bug_report.md&title=).
+
+Follow along with the template and please provide as much information as possible.
+
+# Suggesting a Feature
+
+Before submitting a feature request, check out our [Roadmap](https://github.com/tithely/tithely-transaction-gem/wiki/2020-Roadmap) and active [Projects](https://github.com/tithely/tithely-transaction-gem/projects) to make sure that we aren't currently working on it.
+
+For any other requests, please open an issue [here](https://github.com/tithely/tithely-transaction-gem/issues/new?assignees=&labels=new&template=feature_request.md&title=).
+
+Follow along with the template and please provide as much information as possible.
+
+# Submitting a Pull Request
+
+When submitting a pull request, please follow along with our template and ensure that everything is passing. As a rule, we generally will not take a look at code before all checks have passed.

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+# Summary
+
+
+
+## Checklist
+
+* [ ] Did we think two weeks into the future and not two years? Is this addition malleable to be changed tomorrow without being over-engineered today?
+* [ ] Have you updated the changelog with this behavior?

data/.github/workflows/jeweler.yml

@@ -0,0 +1,11 @@
+name: Jeweler
+
+on:
+  release:
+    types: [ published ]
+
+jobs:
+  jeweler:
+    uses: tithely/gem-workflows/.github/workflows/jeweler.yml@master
+    secrets:
+      GEM_HOST_API_KEY: ${{ secrets.GITHUB_TOKEN }}

data/.github/workflows/puller.yml

@@ -0,0 +1,17 @@
+# Pulls in multiple workflows into a single file for use with PRs.
+name: Puller
+
+on:
+  pull_request:
+    types: [ opened, reopened, synchronize ]
+  workflow_dispatch:
+
+jobs:
+  tester:
+    uses: tithely/gem-workflows/.github/workflows/tester.yml@master
+  editorconfig:
+    uses: tithely/gem-workflows/.github/workflows/editorconfig.yml@master
+  rubocop:
+    uses: tithely/gem-workflows/.github/workflows/rubocop.yml@master
+  yard:
+    uses: tithely/gem-workflows/.github/workflows/yard.yml@master

data/.gitignore

@@ -0,0 +1,16 @@
+/.bundle/
+/.byebug_history
+/.yardoc
+/_yardoc/
+/doc/
+/coverage/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status
+
+.idea/*
+
+.DS_Store

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,227 @@
+require:
+  - rubocop-performance
+  - rubocop-rake
+  - rubocop-rspec
+
+AllCops:
+  # RuboCop has a bunch of cops enabled by default. This setting tells RuboCop
+  # to ignore them, so only the ones explicitly set in this file are enabled.
+  DisabledByDefault: true
+  TargetRubyVersion: 3.0
+
+Performance:
+  Exclude:
+    - "**/test/**/*"
+
+# Prefer &&/|| over and/or.
+Style/AndOr:
+  Enabled: true
+  EnforcedStyle: conditionals
+
+# Align `when` with `case`.
+Layout/CaseIndentation:
+  Enabled: true
+  EnforcedStyle: end
+
+Layout/ClosingHeredocIndentation:
+  Enabled: true
+
+# Align comments with method definitions.
+Layout/CommentIndentation:
+  Enabled: true
+
+Layout/ElseAlignment:
+  Enabled: true
+
+# Align `end` with the matching keyword or starting expression except for
+# assignments, where it should be aligned with the LHS.
+Layout/EndAlignment:
+  Enabled: true
+  EnforcedStyleAlignWith: variable
+  AutoCorrect: true
+
+Layout/EmptyLineAfterMagicComment:
+  Enabled: true
+
+Layout/EmptyLinesAroundAccessModifier:
+  Enabled: false
+  EnforcedStyle: only_before
+
+Layout/EmptyLinesAroundBlockBody:
+  Enabled: true
+
+# In a regular class definition, no empty lines around the body.
+Layout/EmptyLinesAroundClassBody:
+  Enabled: true
+
+# In a regular method definition, no empty lines around the body.
+Layout/EmptyLinesAroundMethodBody:
+  Enabled: true
+
+# In a regular module definition, no empty lines around the body.
+Layout/EmptyLinesAroundModuleBody:
+  Enabled: true
+
+# Use Ruby >= 1.9 syntax for hashes. Prefer { a: :b } over { :a => :b }.
+Style/HashSyntax:
+  Enabled: true
+
+Layout/FirstArgumentIndentation:
+  Enabled: true
+
+# Method definitions after `private` or `protected` isolated calls need one
+# extra level of indentation.
+Layout/IndentationConsistency:
+  Enabled: false
+
+# Two spaces, no tabs (for indentation).
+Layout/IndentationWidth:
+  Enabled: true
+
+Layout/LeadingCommentSpace:
+  Enabled: true
+
+Layout/SpaceAfterColon:
+  Enabled: true
+
+Layout/SpaceAfterComma:
+  Enabled: true
+
+Layout/SpaceAfterSemicolon:
+  Enabled: true
+
+Layout/SpaceAroundEqualsInParameterDefault:
+  Enabled: true
+
+Layout/SpaceAroundKeyword:
+  Enabled: true
+
+Layout/SpaceBeforeComma:
+  Enabled: true
+
+Layout/SpaceBeforeComment:
+  Enabled: true
+
+Layout/SpaceBeforeFirstArg:
+  Enabled: true
+
+Style/DefWithParentheses:
+  Enabled: true
+
+# Defining a method with parameters needs parentheses.
+Style/MethodDefParentheses:
+  Enabled: true
+
+Style/FrozenStringLiteralComment:
+  Enabled: true
+  EnforcedStyle: always
+
+Style/RedundantFreeze:
+  Enabled: true
+
+# Use `foo {}` not `foo{}`.
+Layout/SpaceBeforeBlockBraces:
+  Enabled: true
+
+# Use `foo { bar }` not `foo {bar}`.
+Layout/SpaceInsideBlockBraces:
+  Enabled: true
+  EnforcedStyleForEmptyBraces: space
+
+# Use `{ a: 1 }` not `{a:1}`.
+Layout/SpaceInsideHashLiteralBraces:
+  Enabled: true
+
+Layout/SpaceInsideParens:
+  Enabled: true
+
+# Check quotes usage according to lint rule below.
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+# Detect hard tabs, no hard tabs.
+Layout/IndentationStyle:
+  Enabled: true
+
+# Empty lines should not have any spaces.
+Layout/TrailingEmptyLines:
+  Enabled: true
+
+# No trailing whitespace.
+Layout/TrailingWhitespace:
+  Enabled: true
+
+# Use quotes for string literals when they are enough.
+Style/RedundantPercentQ:
+  Enabled: true
+
+Lint/AmbiguousOperator:
+  Enabled: true
+
+Lint/AmbiguousRegexpLiteral:
+  Enabled: true
+
+Lint/ErbNewArguments:
+  Enabled: true
+
+# Use my_method(my_arg) not my_method( my_arg ) or my_method my_arg.
+Lint/RequireParentheses:
+  Enabled: true
+
+Lint/ShadowingOuterLocalVariable:
+  Enabled: true
+
+Lint/RedundantStringCoercion:
+  Enabled: true
+
+Lint/UriEscapeUnescape:
+  Enabled: true
+
+Lint/UselessAssignment:
+  Enabled: true
+
+Lint/DeprecatedClassMethods:
+  Enabled: true
+
+Style/ParenthesesAroundCondition:
+  Enabled: true
+
+Style/RedundantBegin:
+  Enabled: true
+
+Style/RedundantReturn:
+  Enabled: true
+  AllowMultipleReturnValues: true
+
+Style/Semicolon:
+  Enabled: true
+  AllowAsExpressionSeparator: true
+
+# Prefer Foo.method over Foo::method
+Style/ColonMethodCall:
+  Enabled: true
+
+Style/TrivialAccessors:
+  Enabled: true
+
+Performance/FlatMap:
+  Enabled: true
+
+Performance/RedundantMerge:
+  Enabled: true
+
+Performance/StartWith:
+  Enabled: true
+
+Performance/EndWith:
+  Enabled: true
+
+Performance/RegexpMatch:
+  Enabled: true
+
+Performance/ReverseEach:
+  Enabled: true
+
+Performance/UnfreezeString:
+  Enabled: true

data/.tool-versions

@@ -0,0 +1 @@
+ruby 3.0.6

data/CHANGELOG.md

@@ -0,0 +1,70 @@
+<!-- markdownlint-disable MD024 -->
+
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+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).
+
+## [Unreleased]
+
+### Changed
+
+1. *BREAKING CHANGE* Allowed for newer versions of ActiveSupport for use in projects that are targeting a higher version of Rails.
+
+## [1.1.0] - 2023-11-01
+
+### Changed
+
+1. Rename faithteams-gem to faithteams-api. (IN-2274)
+
+## [1.0.1] - 2023-10-30
+
+### Fixed
+
+1. Fix missing info in code of conduct. (IN-2274)
+
+## [1.0.0] - 2023-10-27
+
+### Changed
+
+1. Prep for publishing publicly. (IN-2274)
+
+## [0.4.1] - 2023-08-31
+
+### Fixed
+
+1. Skip deleted batches when doing a `Batch#find_by_batch`.
+
+## [0.4.0] - 2023-08-29
+
+### Added
+
+1. Add `Resource::ContributionType#find`. (IN-2192)
+1. Split `Connection#request`` into two separate methods: 1) returns the response and 2) makes the request and parses the response. (IN-2192)
+1. Remove duplicate `Connection#authenticate`` in favor of `Resource::User#authenticate`. (IN-2192)
+1. `Deposit#search` now takes any parameter that can be sent to the API. (IN-2192)
+1. `Funds#search` now takes any parameter that can be sent to the API. (IN-2192)
+1. Import and build out ThunderClient tests. (IN-2192)
+
+## [0.3.0] - 2023-06-12
+
+### Added
+
+1. Add contribution type resource and entity. (IN-2108)
+1. Added header? and detail? predicates on ContributionRecords. (IN-2108)
+
+## [0.2.0] - 2023-06-01
+
+### Changed
+
+1. Use activesupport 7.0.5. (IN-2109)
+
+## [0.1.0] - 2023-05-24
+
+### Added
+
+1. Add faithteams api v2 functionality (IN-2110)
+
+<!-- markdownlint-enable MD024 -->

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socioeconomic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement through [Github
+Reporting](https://docs.github.com/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+or by emailing [integrations@tithe.ly](mailto:integrations@tithe.ly?subject=Code of Conduct violation).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/Gemfile

@@ -0,0 +1,6 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in faithteams-api.gemspec
+gemspec