ff-tbl-macros 0.1.8 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 134458580b82af72b8df814edfc9e0ad9a30ee388c3022e18d8cae0f2052176c
-  data.tar.gz: 7ac93a23b408fef75f9f9557cc848863280a8838d9e0adcbd707172f01600029
+  metadata.gz: 90a9f7ef3c844031242e16387a10875ece80e78d8aea61350d160c9b74b9434b
+  data.tar.gz: d212f44a7c217300ea7802c11d504177f976d6f45c4136ccbc3e6e52e3eaac50
 SHA512:
-  metadata.gz: 45456aadf56e6642a389c708ef27157544fe2c2c576715e7a83662c52ace88928056e75aada6722b48a4ababded4bc7021bb3e3eb7ee51e9cd47008289def016
-  data.tar.gz: d6f546fb293f0df15bce02d573821438b773bb8e44dea1aeacdf83addadbcd7c7ec92c0dd5a4b601d9126987bc71a5b9cb0ef05acfad794cd433942a7f2ed57b
+  metadata.gz: b38bb38b0e7f0de043d0ca1a55ac8a8c4fee2f359779c9285f0feed0b63ca104dbd498337800a1c82cc5a4a2541a32e7682017139f007567793e64f6eeb7dff6
+  data.tar.gz: 4cb1d5164e8de2a57fa65c2932e98c73ccb1a00801de18699224cf92be3169602a7292ebe7156ac02e7b3927bc91f78bdc7fc0a4bf1d1342c62606eb967b1813

data/CHANGELOG.md

@@ -0,0 +1,43 @@
+# Changelog
+
+## [Unreleased]
+
+## [1.0.0] - 2019-04-03
+### Changed
+- Update version to 1.0.0
+
+## [0.1.8] - 2019-04-01
+### Fix
+- Resolve offences pointed by Rubocop
+- Update documentation
+- Add missing documentation
+
+### Changed
+- Use rubygems version insted GitHub one
+
+### Added
+- Add Travis setup
+
+## [0.1.6] - 2019-03-28
+### Added
+- Added error related macros
+
+## [0.1.5] - 2019-03-08
+### Added
+- Dockerize project
+
+### Changed
+- Rebuild ExtractParams macro
+
+## [0.1.4] - 2019-03-08
+### Added
+- Add posibility of using custom project macros together with gem ones
+
+## [0.0.7] - 2019-03-07
+### Removed
+- Remove event store related macros
+
+## [0.0.1] - 2019-03-05
+### Added
+- Initial files for the gem
+- Initial set of Macros, for model, contract and current user

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

data/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Introduction
+
+Thank you for considering contributing to this project!
+
+Any kind of contributions will be appreciated, from improving the documentation,
+submitting bug reports and feature requests or writing useful checks.
+
+# Ground Rules
+
+* Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get feedback.
+* Keep pull requests as small as possible, preferably one new feature per pull request.
+
+# Your First Contribution
+
+Unsure where to begin contributing? Here you have some ideas:
+
+* documentation is always welcome
+* check the pending issues
+* write new useful macros
+
+# Getting started
+
+1. Clone the repository if you have commit rights or create your own fork otherwise
+1. Create your Feature Branch (git checkout -b feature/AmazingFeature)
+1. Commit your Changes (git commit -m 'Add some AmazingFeature)
+1. Push to the Branch (git push origin feature/AmazingFeature)
+1. Open a Pull Request
+
+Be sure you have followed the code style for the project.
+
+# How to report a bug
+
+If you find a security vulnerability, do NOT open an issue. Email security@firefield.com instead.
+
+When filing an issue, make sure to answer these questions:
+
+1. What did you do?
+1. What did you expect to see?
+1. What did you see instead?
+
+# How to suggest a feature or enhancement
+
+Open an issue on our issues list which describes the feature you would like to
+see, why you need it, and how it should work.
+
+# Code review process
+
+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

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    ff-tbl-macros (0.1.8)
+    ff-tbl-macros (1.0.0)
       activesupport (~> 5.2)
       require_all (~> 2.0)
       trailblazer (~> 2.0)

data/README.md

@@ -1,6 +1,6 @@
 # ff-tbl-macros
 
-![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)
+![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)
 
 Macros for Trailblazer operations.
 
@@ -22,7 +22,7 @@ For contributing, install docker to use the provided dockerized development envi
 Add this line to your application's Gemfile:
 
 ```ruby
-gem 'ff-tbl-macros', git: 'https://github.com/firefield/ff-tbl-macros.git'
+gem 'ff-tbl-macros'
 ```
 
 # Usage
@@ -37,11 +37,7 @@ end
 
 # Contributing
 
-1. Fork the Project
-1. Create your Feature Branch (git checkout -b feature/AmazingFeature)
-1. Commit your Changes (git commit -m 'Add some AmazingFeature)
-1. Push to the Branch (git push origin feature/AmazingFeature)
-1. Open a Pull Request
+Use the provided dockerized development environment. For more information check the [CONTRIBUTING](CONTRIBUTING.md) file.
 
 ## Development
 

data/lib/macros/ctx/inspect.rb

@@ -18,9 +18,9 @@ module Macros
 
       def call(ctx, **)
         if @key
-          p ctx[@key]
+          p ctx[@key] # rubocop:disable Rails/Output
         else
-          p ctx
+          p ctx # rubocop:disable Rails/Output
         end
       end
     end

data/lib/macros/version.rb

@@ -1,6 +1,5 @@
 # frozen_string_literal: true
 
 module Macros
-  # Current version
-  VERSION = '0.1.8'
+  VERSION = '1.0.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ff-tbl-macros
 version: !ruby/object:Gem::Version
-  version: 0.1.8
+  version: 1.0.0
 platform: ruby
 authors:
 - Artur Szwed, Claudio Perez Gamayo
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-04-02 00:00:00.000000000 Z
+date: 2019-04-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -59,10 +59,13 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- CONTRIBUTING.md
 - Dockerfile
 - Gemfile
 - Gemfile.lock
-- MIT-LICENSE
+- LICENSE
 - README.md
 - lib/ff-tbl-macros.rb
 - lib/macros/auth.rb