Sqooba / scala-timeseries-lib / 114

Build # 114

Build Type

push

travis-ci-com

Committed by OSAG OS Code

Commit Message

<a href="https://github.com/Sqooba/scala-timeseries-lib/commit/0d3ba30e8">Add type param to tsid

GitOrigin-RevId: </a><a class="double-link" href="https://github.com/Sqooba/scala-timeseries-lib/commit/128171411">128171411</a>

Run Details

1 of 1 new or added line in 1 file covered. (100.0%)

959 of 1047 relevant lines covered (91.6%)

1.83 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

0.0

/src/main/scala/io/sqooba/oss/timeseries/entity/TimeSeriesEntityId.scala

package io.sqooba.oss.timeseries.entity

/** Identifies an entity that can have time series data attached to it. The different
 * possible signals are defined by [[io.sqooba.oss.timeseries.entity.TsLabel!]]s.
 *
 * @note It is the implementor's responsibility to choose a way of identifying
 * entities. Be that by different type, numerical or lexical identifiers. The idea is
 * that users define the identifying attributes on their implementation of the trait.
 */
// Not requiring a specific type and shape of identifying property leaves the choice
// to the user and also enables use-cases where multiple identifying mechanisms need
// to be combined with trait polymorphism.
trait TimeSeriesEntityId {

  /**
   * @param signal the label of the time series signal
   * @return a TsId that fully identifies a time series signal of a the entity
   *         specified by this EntityId
   */
  // TODO: the use of this function probably causes AnyVal implementations to require an
  //   instantiation. At the moment we mostly care about correctness, not performance, but
  //   we need to keep it in mind. If at some point we want to do things allocation-free,
  //   have a look at https://docs.scala-lang.org/overviews/core/value-classes.html under
  //   the extension methods paragraph
  def buildTsId(signal: TsLabel): TsId[this.type] = TsId(this, signal)
}

1	package io.sqooba.oss.timeseries.entity
2
3	/** Identifies an entity that can have time series data attached to it. The different
4	* possible signals are defined by [[io.sqooba.oss.timeseries.entity.TsLabel!]]s.
5	*
6	* @note It is the implementor's responsibility to choose a way of identifying
7	* entities. Be that by different type, numerical or lexical identifiers. The idea is
8	* that users define the identifying attributes on their implementation of the trait.
9	*/
10	// Not requiring a specific type and shape of identifying property leaves the choice
11	// to the user and also enables use-cases where multiple identifying mechanisms need
12	// to be combined with trait polymorphism.
13	trait TimeSeriesEntityId {
14
15	/**
16	* @param signal the label of the time series signal
17	* @return a TsId that fully identifies a time series signal of a the entity
18	* specified by this EntityId
19	*/
20	// TODO: the use of this function probably causes AnyVal implementations to require an
21	// instantiation. At the moment we mostly care about correctness, not performance, but
22	// we need to keep it in mind. If at some point we want to do things allocation-free,
23	// have a look at https://docs.scala-lang.org/overviews/core/value-classes.html under
24	// the extension methods paragraph
25	def buildTsId(signal: TsLabel): TsId[this.type] = TsId(this, signal)	×
26	}

Sqooba / scala-timeseries-lib / 114

Source File Press 'n' to go to next uncovered line, 'b' for previous

Source File
Press 'n' to go to next uncovered line, 'b' for previous