Problem
Some of our transformers & estimators are not thoroughly tested or not tested at all.

Solution
Use OpTransformerSpec and OpEstimatorSpec base test specs to provide tests for all existing transformers & estimators.

🏗 Enhancement Proposal

Provide more information on where to put the Initilize() method for iOS and Android.

For iOS in AppDelegate:

public override bool FinishedLaunching(UIApplication app, NSDictionary options)
{
    Xamarin.Forms.Forms.Init();
    var config = new FFImageLoading.Config.Configuration()
    {
        VerboseLogging = false,
        VerbosePerformanceLogging = fa

1. Create 'Cube', 'Cube.001', 'Cube.002'. Create collection 'Collection 1'.
2. Move 'Cube.002' into 'Collection 1'.
3. Exclude 'Collection 1' by clicking the check box on its left.
4. Goto 'Quick Align Planes' Grab Destination of 'Cube'.
5. Select 'Cube.001' select three points and hit 'Apply to Object' button.
6. Get error message "Object Cube.002 not in View layer 'View layer'".

This comment in the source file RrbTree.java:

    // (MIN_NODE_LENGTH + MAX_NODE_LENGTH) / 2 should equal
    // STRICT_NODE_LENGTH so that they have the same average node size
    // to make the index interpolation easier.

confuses me. The values I see for these constants are:

 NODE_LENGTH_POW_2 5 
 STRICT_NODE_LENGTH 32 
 HALF_STRICT_NODE_LENGTH 16 
 MIN_NODE_LENGTH 22 

Hi,
I have installed this library via pip, while checking out the official page, I noticed that the documentation page gives a 404 page not found error. Is there a way to refer to the official documentation for this library? I want to use it to model a robot using Python as the original library d

The readme stated for the timestamp the following syntax:

{
  "operation": "timestamp",
  "timestamp[0]": {
    "inputFormat": "Mon Jan _2 15:04:05 -0700 2006",
    "outputFormat": "2006-01-02T15:04:05-0700"
  },
  "nowTimestamp": {
    "inputFormat": "$now",
    "outputFormat": "2006-01-02T15:04:05-0700"
  },
  "epochTimestamp": {
    "inputFormat": "2006-01-02T15:04:05-0700"

The Point#d, Vector#d and Direction#d modules were recently optimized in the coordinate-systems branch to avoid unnecessary object allocations and function calls, but this also meant most functions got more verbose and therefore more prone to typos. It would be very useful to add some more fuzz and/or hardcoded tests for the various functions in these modules, following the patterns in the

We're using rmwc components with material UI. This doesn't work as expected because of your tagMap:

import { Button } from 'rmwc'
<ReactFilestack
  componentDisplayMode={{
    type: Button
  }}
/>

As the ReactFilestack component only renders the button, optimally I would expect the API to be something like this..

import { Button } from 'rmwc'
<ReactFilestack

i'm trying to compare this package to mississippi

Do you think it makes sense to add some unit examples to your code base of what you think a normal usage pattern is - so that I can make the case of if this make sense for my use case - or keep using the ol'mississippi

Ref
1: npm.im/mississippi

There should be a better way to manage deployments across multiple clients