ff-tbl-macros 0.1.8 → 1.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +43 -0
- data/CODE_OF_CONDUCT.md +76 -0
- data/CONTRIBUTING.md +48 -0
- data/Gemfile.lock +1 -1
- data/{MIT-LICENSE → LICENSE} +0 -0
- data/README.md +3 -7
- data/lib/macros/ctx/inspect.rb +2 -2
- data/lib/macros/version.rb +1 -2
- metadata +6 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 90a9f7ef3c844031242e16387a10875ece80e78d8aea61350d160c9b74b9434b
|
4
|
+
data.tar.gz: d212f44a7c217300ea7802c11d504177f976d6f45c4136ccbc3e6e52e3eaac50
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b38bb38b0e7f0de043d0ca1a55ac8a8c4fee2f359779c9285f0feed0b63ca104dbd498337800a1c82cc5a4a2541a32e7682017139f007567793e64f6eeb7dff6
|
7
|
+
data.tar.gz: 4cb1d5164e8de2a57fa65c2932e98c73ccb1a00801de18699224cf92be3169602a7292ebe7156ac02e7b3927bc91f78bdc7fc0a4bf1d1342c62606eb967b1813
|
data/CHANGELOG.md
ADDED
@@ -0,0 +1,43 @@
|
|
1
|
+
# Changelog
|
2
|
+
|
3
|
+
## [Unreleased]
|
4
|
+
|
5
|
+
## [1.0.0] - 2019-04-03
|
6
|
+
### Changed
|
7
|
+
- Update version to 1.0.0
|
8
|
+
|
9
|
+
## [0.1.8] - 2019-04-01
|
10
|
+
### Fix
|
11
|
+
- Resolve offences pointed by Rubocop
|
12
|
+
- Update documentation
|
13
|
+
- Add missing documentation
|
14
|
+
|
15
|
+
### Changed
|
16
|
+
- Use rubygems version insted GitHub one
|
17
|
+
|
18
|
+
### Added
|
19
|
+
- Add Travis setup
|
20
|
+
|
21
|
+
## [0.1.6] - 2019-03-28
|
22
|
+
### Added
|
23
|
+
- Added error related macros
|
24
|
+
|
25
|
+
## [0.1.5] - 2019-03-08
|
26
|
+
### Added
|
27
|
+
- Dockerize project
|
28
|
+
|
29
|
+
### Changed
|
30
|
+
- Rebuild ExtractParams macro
|
31
|
+
|
32
|
+
## [0.1.4] - 2019-03-08
|
33
|
+
### Added
|
34
|
+
- Add posibility of using custom project macros together with gem ones
|
35
|
+
|
36
|
+
## [0.0.7] - 2019-03-07
|
37
|
+
### Removed
|
38
|
+
- Remove event store related macros
|
39
|
+
|
40
|
+
## [0.0.1] - 2019-03-05
|
41
|
+
### Added
|
42
|
+
- Initial files for the gem
|
43
|
+
- Initial set of Macros, for model, contract and current user
|
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,76 @@
|
|
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, sex characteristics, gender identity and expression,
|
9
|
+
level of experience, education, socio-economic status, nationality, personal
|
10
|
+
appearance, race, religion, or sexual identity 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
|
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 within all project spaces, and it also applies when
|
49
|
+
an individual is representing the project or its community in public spaces.
|
50
|
+
Examples of representing a project or community include using an official
|
51
|
+
project e-mail address, posting via an official social media account, or acting
|
52
|
+
as an appointed representative at an online or offline event. Representation of
|
53
|
+
a project may be 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 [INSERT EMAIL ADDRESS]. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
|
72
|
+
|
73
|
+
[homepage]: https://www.contributor-covenant.org
|
74
|
+
|
75
|
+
For answers to common questions about this code of conduct, see
|
76
|
+
https://www.contributor-covenant.org/faq
|
data/CONTRIBUTING.md
ADDED
@@ -0,0 +1,48 @@
|
|
1
|
+
# Introduction
|
2
|
+
|
3
|
+
Thank you for considering contributing to this project!
|
4
|
+
|
5
|
+
Any kind of contributions will be appreciated, from improving the documentation,
|
6
|
+
submitting bug reports and feature requests or writing useful checks.
|
7
|
+
|
8
|
+
# Ground Rules
|
9
|
+
|
10
|
+
* Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get feedback.
|
11
|
+
* Keep pull requests as small as possible, preferably one new feature per pull request.
|
12
|
+
|
13
|
+
# Your First Contribution
|
14
|
+
|
15
|
+
Unsure where to begin contributing? Here you have some ideas:
|
16
|
+
|
17
|
+
* documentation is always welcome
|
18
|
+
* check the pending issues
|
19
|
+
* write new useful macros
|
20
|
+
|
21
|
+
# Getting started
|
22
|
+
|
23
|
+
1. Clone the repository if you have commit rights or create your own fork otherwise
|
24
|
+
1. Create your Feature Branch (git checkout -b feature/AmazingFeature)
|
25
|
+
1. Commit your Changes (git commit -m 'Add some AmazingFeature)
|
26
|
+
1. Push to the Branch (git push origin feature/AmazingFeature)
|
27
|
+
1. Open a Pull Request
|
28
|
+
|
29
|
+
Be sure you have followed the code style for the project.
|
30
|
+
|
31
|
+
# How to report a bug
|
32
|
+
|
33
|
+
If you find a security vulnerability, do NOT open an issue. Email security@firefield.com instead.
|
34
|
+
|
35
|
+
When filing an issue, make sure to answer these questions:
|
36
|
+
|
37
|
+
1. What did you do?
|
38
|
+
1. What did you expect to see?
|
39
|
+
1. What did you see instead?
|
40
|
+
|
41
|
+
# How to suggest a feature or enhancement
|
42
|
+
|
43
|
+
Open an issue on our issues list which describes the feature you would like to
|
44
|
+
see, why you need it, and how it should work.
|
45
|
+
|
46
|
+
# Code review process
|
47
|
+
|
48
|
+
The core team looks at Pull Requests on a regular basis. After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity.
|
data/Gemfile.lock
CHANGED
data/{MIT-LICENSE → LICENSE}
RENAMED
File without changes
|
data/README.md
CHANGED
@@ -1,6 +1,6 @@
|
|
1
1
|
# ff-tbl-macros
|
2
2
|
|
3
|
-
![MIT-LICENSE](https://img.shields.io/github/license/firefield/ff-tbl-macros.svg?style=flat-square) ![build status](https://img.shields.io/travis/firefield/ff-tbl-macros.svg?style=flat-square)
|
3
|
+
![MIT-LICENSE](https://img.shields.io/github/license/firefield/ff-tbl-macros.svg?style=flat-square) [![Gem Version](https://img.shields.io/gem/v/ff-tbl-macros.svg?style=flat-square)](https://rubygems.org/gems/ff-tbl-macros) ![build status](https://img.shields.io/travis/firefield/ff-tbl-macros.svg?style=flat-square)
|
4
4
|
|
5
5
|
Macros for Trailblazer operations.
|
6
6
|
|
@@ -22,7 +22,7 @@ For contributing, install docker to use the provided dockerized development envi
|
|
22
22
|
Add this line to your application's Gemfile:
|
23
23
|
|
24
24
|
```ruby
|
25
|
-
gem 'ff-tbl-macros'
|
25
|
+
gem 'ff-tbl-macros'
|
26
26
|
```
|
27
27
|
|
28
28
|
# Usage
|
@@ -37,11 +37,7 @@ end
|
|
37
37
|
|
38
38
|
# Contributing
|
39
39
|
|
40
|
-
|
41
|
-
1. Create your Feature Branch (git checkout -b feature/AmazingFeature)
|
42
|
-
1. Commit your Changes (git commit -m 'Add some AmazingFeature)
|
43
|
-
1. Push to the Branch (git push origin feature/AmazingFeature)
|
44
|
-
1. Open a Pull Request
|
40
|
+
Use the provided dockerized development environment. For more information check the [CONTRIBUTING](CONTRIBUTING.md) file.
|
45
41
|
|
46
42
|
## Development
|
47
43
|
|
data/lib/macros/ctx/inspect.rb
CHANGED
data/lib/macros/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: ff-tbl-macros
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 1.0.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Artur Szwed, Claudio Perez Gamayo
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2019-04-
|
11
|
+
date: 2019-04-03 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: activesupport
|
@@ -59,10 +59,13 @@ executables: []
|
|
59
59
|
extensions: []
|
60
60
|
extra_rdoc_files: []
|
61
61
|
files:
|
62
|
+
- CHANGELOG.md
|
63
|
+
- CODE_OF_CONDUCT.md
|
64
|
+
- CONTRIBUTING.md
|
62
65
|
- Dockerfile
|
63
66
|
- Gemfile
|
64
67
|
- Gemfile.lock
|
65
|
-
-
|
68
|
+
- LICENSE
|
66
69
|
- README.md
|
67
70
|
- lib/ff-tbl-macros.rb
|
68
71
|
- lib/macros/auth.rb
|