voltage 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.github/CODEOWNERS +4 -0
- data/.github/FUNDING.yml +4 -0
- data/.github/ISSUE_TEMPLATE/bug_report.md +41 -0
- data/.github/ISSUE_TEMPLATE/feature_request.md +23 -0
- data/.github/PULL_REQUEST_TEMPLATE.md +38 -0
- data/.github/dependabot.yml +15 -0
- data/.github/workflows/ruby-tests.yml +53 -0
- data/.gitignore +17 -0
- data/.rubocop.yml +12 -0
- data/CHANGELOG.md +16 -0
- data/CODE_OF_CONDUCT.md +75 -0
- data/CONTRIBUTING.md +80 -0
- data/Gemfile +4 -0
- data/LICENSE.txt +22 -0
- data/README.md +299 -0
- data/Rakefile +15 -0
- data/examples/activerecord_model.rb +43 -0
- data/examples/arguments.rb +19 -0
- data/examples/block_context.rb +23 -0
- data/examples/blocks.rb +18 -0
- data/examples/call.rb +23 -0
- data/examples/chain.rb +58 -0
- data/examples/listener.rb +30 -0
- data/lib/voltage/extensions/active_record.rb +60 -0
- data/lib/voltage/extensions/call.rb +25 -0
- data/lib/voltage/listener.rb +27 -0
- data/lib/voltage/mock.rb +51 -0
- data/lib/voltage/version.rb +5 -0
- data/lib/voltage.rb +49 -0
- data/voltage.gemspec +35 -0
- metadata +187 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 882dca60113d6a9a50264801155a7cfa38c648f82a96af1fbed9d776135586ac
|
4
|
+
data.tar.gz: a342fb641bb7ed2c5c414520d8510667743367228fc29c04f0903ee989f76dbd
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: b0764d3fe77052d4665abe39d8a6743f26ba79bc6f613d3d97a4a4c7cac163dd4e97292aa7a6ad098c588b52d216fdcd9cbdebb0eb88f47945d24b0439591347
|
7
|
+
data.tar.gz: badbce6d056a9f107c081872722a4780dd4233bd5b2c79045a12bd0d3346e2aa18e7933fa9c2e7ef2c70692729f11cddf0afda6341a5768bb55451ecbe35b185
|
data/.github/CODEOWNERS
ADDED
data/.github/FUNDING.yml
ADDED
@@ -0,0 +1,41 @@
|
|
1
|
+
---
|
2
|
+
name: "🐛 Bug Report"
|
3
|
+
about: Report a reproducible bug or regression.
|
4
|
+
title: 'Bug: '
|
5
|
+
labels: 'Status: Unconfirmed'
|
6
|
+
|
7
|
+
---
|
8
|
+
|
9
|
+
<!--
|
10
|
+
- Please provide a clear and concise description of what the bug is.
|
11
|
+
- If possible, add an example reproducing your issue.
|
12
|
+
- Please test using the latest version of rails_env
|
13
|
+
to make sure your issue has not already been fixed.
|
14
|
+
-->
|
15
|
+
|
16
|
+
## Description
|
17
|
+
|
18
|
+
[Add bug description here]
|
19
|
+
|
20
|
+
## How to reproduce
|
21
|
+
|
22
|
+
[Add steps on how to reproduce this issue]
|
23
|
+
|
24
|
+
## What do you expect
|
25
|
+
|
26
|
+
[Describe what do you expect to happen]
|
27
|
+
|
28
|
+
## What happened instead
|
29
|
+
|
30
|
+
[Describe the actual results]
|
31
|
+
|
32
|
+
## Software:
|
33
|
+
|
34
|
+
- Gem version: [Add gem version here]
|
35
|
+
- Ruby version: [Add version here]
|
36
|
+
|
37
|
+
## Full backtrace
|
38
|
+
|
39
|
+
```text
|
40
|
+
[Paste full backtrace here]
|
41
|
+
```
|
@@ -0,0 +1,23 @@
|
|
1
|
+
---
|
2
|
+
name: "💡 Feature request"
|
3
|
+
about: Have an idea that may be useful? Make a suggestion!
|
4
|
+
title: 'Feature Request: '
|
5
|
+
labels: 'Feature request'
|
6
|
+
|
7
|
+
---
|
8
|
+
|
9
|
+
## Description
|
10
|
+
|
11
|
+
_A clear and concise description of what the problem is._
|
12
|
+
|
13
|
+
## Describe the solution
|
14
|
+
|
15
|
+
_A clear and concise description of what you want to happen._
|
16
|
+
|
17
|
+
## Alternatives you considered
|
18
|
+
|
19
|
+
_A clear and concise description of any alternative solutions or features you've considered._
|
20
|
+
|
21
|
+
## Additional context
|
22
|
+
|
23
|
+
_Add any other context, screenshots, links, etc about the feature request here._
|
@@ -0,0 +1,38 @@
|
|
1
|
+
<!--
|
2
|
+
If you're making a doc PR or something tiny where the below is irrelevant,
|
3
|
+
delete this template and use a short description, but in your description aim to
|
4
|
+
include both what the change is, and why it is being made, with enough context
|
5
|
+
for anyone to understand.
|
6
|
+
-->
|
7
|
+
|
8
|
+
<details>
|
9
|
+
<summary>PR Checklist</summary>
|
10
|
+
|
11
|
+
### PR Structure
|
12
|
+
|
13
|
+
- [ ] This PR has reasonably narrow scope (if not, break it down into smaller
|
14
|
+
PRs).
|
15
|
+
- [ ] This PR avoids mixing refactoring changes with feature changes (split into
|
16
|
+
two PRs otherwise).
|
17
|
+
- [ ] This PR's title starts is concise and descriptive.
|
18
|
+
|
19
|
+
### Thoroughness
|
20
|
+
|
21
|
+
- [ ] This PR adds tests for the most critical parts of the new functionality or
|
22
|
+
fixes.
|
23
|
+
- [ ] I've updated any docs, `.md` files, etc… affected by this change.
|
24
|
+
|
25
|
+
</details>
|
26
|
+
|
27
|
+
### What
|
28
|
+
|
29
|
+
[TODO: Short statement about what is changing.]
|
30
|
+
|
31
|
+
### Why
|
32
|
+
|
33
|
+
[TODO: Why this change is being made. Include any context required to understand
|
34
|
+
the why.]
|
35
|
+
|
36
|
+
### Known limitations
|
37
|
+
|
38
|
+
[TODO or N/A]
|
@@ -0,0 +1,15 @@
|
|
1
|
+
---
|
2
|
+
# Documentation:
|
3
|
+
# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
|
4
|
+
|
5
|
+
version: 2
|
6
|
+
updates:
|
7
|
+
- package-ecosystem: "github-actions"
|
8
|
+
directory: "/"
|
9
|
+
schedule:
|
10
|
+
interval: "daily"
|
11
|
+
|
12
|
+
- package-ecosystem: "bundler"
|
13
|
+
directory: "/"
|
14
|
+
schedule:
|
15
|
+
interval: "daily"
|
@@ -0,0 +1,53 @@
|
|
1
|
+
---
|
2
|
+
name: ruby-tests
|
3
|
+
|
4
|
+
on:
|
5
|
+
pull_request:
|
6
|
+
push:
|
7
|
+
workflow_dispatch:
|
8
|
+
inputs: {}
|
9
|
+
|
10
|
+
jobs:
|
11
|
+
build:
|
12
|
+
name: Tests with Ruby ${{ matrix.ruby }} and ${{ matrix.gemfile }}
|
13
|
+
runs-on: "ubuntu-latest"
|
14
|
+
strategy:
|
15
|
+
fail-fast: false
|
16
|
+
matrix:
|
17
|
+
ruby: ["2.7", "3.0"]
|
18
|
+
gemfile:
|
19
|
+
- Gemfile
|
20
|
+
|
21
|
+
steps:
|
22
|
+
- uses: actions/checkout@v2.4.0
|
23
|
+
|
24
|
+
- uses: actions/cache@v2.1.7
|
25
|
+
with:
|
26
|
+
path: vendor/bundle
|
27
|
+
key: >
|
28
|
+
${{ runner.os }}-${{ matrix.ruby }}-gems-${{
|
29
|
+
hashFiles(matrix.gemfile) }}
|
30
|
+
restore-keys: >
|
31
|
+
${{ runner.os }}-${{ matrix.ruby }}-gems-${{
|
32
|
+
hashFiles(matrix.gemfile) }}
|
33
|
+
|
34
|
+
- name: Set up Ruby
|
35
|
+
uses: ruby/setup-ruby@v1
|
36
|
+
with:
|
37
|
+
ruby-version: ${{ matrix.ruby }}
|
38
|
+
|
39
|
+
- name: Install gem dependencies
|
40
|
+
env:
|
41
|
+
BUNDLE_GEMFILE: ${{ matrix.gemfile }}
|
42
|
+
run: |
|
43
|
+
gem install bundler
|
44
|
+
bundle config path vendor/bundle
|
45
|
+
bundle update --jobs 4 --retry 3
|
46
|
+
|
47
|
+
- name: Run Tests
|
48
|
+
env:
|
49
|
+
PGHOST: localhost
|
50
|
+
PGUSER: postgres
|
51
|
+
BUNDLE_GEMFILE: ${{ matrix.gemfile }}
|
52
|
+
run: |
|
53
|
+
bundle exec rake
|
data/.gitignore
ADDED
data/.rubocop.yml
ADDED
data/CHANGELOG.md
ADDED
@@ -0,0 +1,16 @@
|
|
1
|
+
# Changelog
|
2
|
+
|
3
|
+
<!--
|
4
|
+
Prefix your message with one of the following:
|
5
|
+
|
6
|
+
- [Added] for new features.
|
7
|
+
- [Changed] for changes in existing functionality.
|
8
|
+
- [Deprecated] for soon-to-be removed features.
|
9
|
+
- [Removed] for now removed features.
|
10
|
+
- [Fixed] for any bug fixes.
|
11
|
+
- [Security] in case of vulnerabilities.
|
12
|
+
-->
|
13
|
+
|
14
|
+
## v0.1.0 - 2021-12-20
|
15
|
+
|
16
|
+
- Initial release.
|
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,75 @@
|
|
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
|
9
|
+
experience, nationality, personal appearance, race, religion, or sexual identity
|
10
|
+
and 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 reject
|
41
|
+
comments, commits, code, wiki edits, issues, and other contributions that are
|
42
|
+
not aligned to this Code of Conduct, or to ban temporarily or permanently any
|
43
|
+
contributor for other behaviors that they deem inappropriate, threatening,
|
44
|
+
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 me@fnando.com. All complaints will be
|
59
|
+
reviewed and investigated and will result in a response that is deemed necessary
|
60
|
+
and appropriate to the circumstances. The project team is obligated to maintain
|
61
|
+
confidentiality with regard to the reporter of an incident. Further details of
|
62
|
+
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],
|
71
|
+
version 1.4, available at
|
72
|
+
[https://contributor-covenant.org/version/1/4][version]
|
73
|
+
|
74
|
+
[homepage]: https://contributor-covenant.org
|
75
|
+
[version]: https://contributor-covenant.org/version/1/4/
|
data/CONTRIBUTING.md
ADDED
@@ -0,0 +1,80 @@
|
|
1
|
+
# Contributing to voltage
|
2
|
+
|
3
|
+
👍🎉 First off, thanks for taking the time to contribute! 🎉👍
|
4
|
+
|
5
|
+
The following is a set of guidelines for contributing to this project. These are
|
6
|
+
mostly guidelines, not rules. Use your best judgment, and feel free to propose
|
7
|
+
changes to this document in a pull request.
|
8
|
+
|
9
|
+
## Code of Conduct
|
10
|
+
|
11
|
+
Everyone interacting in this project's codebases, issue trackers, chat rooms and
|
12
|
+
mailing lists is expected to follow the
|
13
|
+
[code of conduct](https://github.com/fnando/voltage/blob/main/CODE_OF_CONDUCT.md).
|
14
|
+
|
15
|
+
## Reporting bugs
|
16
|
+
|
17
|
+
This section guides you through submitting a bug report. Following these
|
18
|
+
guidelines helps maintainers and the community understand your report, reproduce
|
19
|
+
the behavior, and find related reports.
|
20
|
+
|
21
|
+
- Before creating bug reports, please check the open issues; somebody may
|
22
|
+
already have submitted something similar, and you may not need to create a new
|
23
|
+
one.
|
24
|
+
- When you are creating a bug report, please include as many details as
|
25
|
+
possible, with an example reproducing the issue.
|
26
|
+
|
27
|
+
## Contributing with code
|
28
|
+
|
29
|
+
Before making any radicals changes, please make sure you discuss your intention
|
30
|
+
by [opening an issue on Github](https://github.com/fnando/voltage/issues).
|
31
|
+
|
32
|
+
When you're ready to make your pull request, follow checklist below to make sure
|
33
|
+
your contribution is according to how this project works.
|
34
|
+
|
35
|
+
1. [Fork](https://help.github.com/forking/) voltage
|
36
|
+
2. Create a topic branch - `git checkout -b my_branch`
|
37
|
+
3. Make your changes using [descriptive commit messages](#commit-messages)
|
38
|
+
4. Update CHANGELOG.md describing your changes by adding an entry to the
|
39
|
+
"Unreleased" section. If this section is not available, create one right
|
40
|
+
before the last version.
|
41
|
+
5. Push to your branch - `git push origin my_branch`
|
42
|
+
6. [Create a pull request](https://docs.github.com/articles/creating-a-pull-request)
|
43
|
+
7. That's it!
|
44
|
+
|
45
|
+
## Styleguides
|
46
|
+
|
47
|
+
### Commit messages
|
48
|
+
|
49
|
+
- Use the present tense ("Add feature" not "Added feature")
|
50
|
+
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
|
51
|
+
- Limit the first line to 72 characters or less
|
52
|
+
- Reference issues and pull requests liberally after the first line
|
53
|
+
|
54
|
+
### Changelog
|
55
|
+
|
56
|
+
- Add a message describing your changes to the "Unreleased" section. The
|
57
|
+
changelog message should follow the same style as the commit message.
|
58
|
+
- Prefix your message with one of the following:
|
59
|
+
- `[Added]` for new features.
|
60
|
+
- `[Changed]` for changes in existing functionality.
|
61
|
+
- `[Deprecated]` for soon-to-be removed features.
|
62
|
+
- `[Removed]` for now removed features.
|
63
|
+
- `[Fixed]` for any bug fixes.
|
64
|
+
- `[Security]` in case of vulnerabilities.
|
65
|
+
|
66
|
+
### Ruby code
|
67
|
+
|
68
|
+
- This project uses [Rubocop](https://rubocop.org) to enforce code style. Before
|
69
|
+
submitting your changes, make sure your tests are passing and code conforms to
|
70
|
+
the expected style by running `rake`.
|
71
|
+
- Do not change the library version. This will be done by the maintainer
|
72
|
+
whenever a new version is about to be released.
|
73
|
+
|
74
|
+
### JavaScript code
|
75
|
+
|
76
|
+
- This project uses [ESLint](https://eslint.org) to enforce code style. Before
|
77
|
+
submitting your changes, make sure your tests are passing and code conforms to
|
78
|
+
the expected style by running `yarn test:ci`.
|
79
|
+
- Do not change the library version. This will be done by the maintainer
|
80
|
+
whenever a new version is about to be released.
|
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,22 @@
|
|
1
|
+
Copyright (c) 2021 Nando Vieira
|
2
|
+
|
3
|
+
MIT License
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining
|
6
|
+
a copy of this software and associated documentation files (the
|
7
|
+
"Software"), to deal in the Software without restriction, including
|
8
|
+
without limitation the rights to use, copy, modify, merge, publish,
|
9
|
+
distribute, sublicense, and/or sell copies of the Software, and to
|
10
|
+
permit persons to whom the Software is furnished to do so, subject to
|
11
|
+
the following conditions:
|
12
|
+
|
13
|
+
The above copyright notice and this permission notice shall be
|
14
|
+
included in all copies or substantial portions of the Software.
|
15
|
+
|
16
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
17
|
+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
18
|
+
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
|
19
|
+
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
|
20
|
+
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
|
21
|
+
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
|
22
|
+
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|