stale/intervals
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added travis integration

Browse Source
This commit is contained in:
Daniel Gil 2018-07-03 11:37:29 +02:00
parent 59657e8ba8
commit 81987af8d7
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG.md
View File

@ -1,4 +1,4 @@
# Changelog
## [0.0.1] - 2018-07-03
## [0.1.0] - 2018-07-03
- First release

4
README.md
View File

@ -1,4 +1,4 @@
# intervals [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![GoDoc](https://godoc.org/github.com/centraldereservas/intervals?status.svg)](https://godoc.org/github.com/centraldereservas/intervals)
# intervals [![Build Status](https://travis-ci.org/centraldereservas/intervals.svg?branch=master)](https://travis-ci.org/centraldereservas/intervals) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![GoDoc](https://godoc.org/github.com/centraldereservas/intervals?status.svg)](https://godoc.org/github.com/centraldereservas/intervals)
Provides a helper to work with integer intervals detecting gaps, merged and overlapped sections.
@ -12,7 +12,7 @@ go get github.com/centraldereservas/intervals
Why we need to have control over a list of intervals?
Because provider API's have product prices depending on the age, so they assign a price amount to different age bands.
Because the API providers have their product prices depending on the age, so they assign a price amount to different age bands.
As a result we have a bunch of age bands (with its corresponding price) which can have: