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.

Steps:

1. Go to https://transform.tools/graphql-to-components
2. In the right editor panel, click on the title. It's a select input. Then select TypeScript Apollo Angular

🏗 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

You explain very well on how to use it, but not what it actually does/how it gets done what it does. It's all relatively small, so I (think I) figured it out by glancing at the source, still would be nice if you could expand.

• const MAX_INT = 2147483647; Does that include this Mersenne prime or one less?
• why chmod 755? Everyone should be able to execute/recalculate the ids?

User story.
As a Prism CLI user, I can supply --verbose (or --debug) CLI option, so that I can see more verbose logs.

Is your feature request related to a problem?
There are occasions when I do not have easy access to request or response payload. For those cases, it would be helpful if I could see the actual request and response payloads together with headers. That should help me debu

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 

Using the SlowCheetah task imported from a network path doesn't work.

This was introduced with the following commit: microsoft/slow-cheetah@d6c9cf7

Reading through the Microsoft docs, they say that the MSBuildThisFileDirectory includ

I have tried many functions and they simply made hard everything.
for example:

import robopy.base.transforms as transforms
transforms.eul2r(phi=deg, theta=deg, psi=deg,unit='deg')

But it won't work. Because your degree should be a matrix of numpy with shape [1,1]. And it is not rational and documentation is not providing any information about this.

Using: go version go1.11.1 linux/amd64 in a known-working environment.

On the page/section: https://godoc.org/gopkg.in/qntfy/kazaam.v3#Config.RegisterTransform

The example block shown, when copied and used verbatim, produces:

cannot use func literal (type func(*"gopkg.in/qntfy/kazaam.v3/transform".Config, []byte) ([]byte, error)) as type kazaam.TransformFunc in argument to kc.R

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

Description
As per today, the test coverage is: 97,3%, the purpose of this task is to reach 100%.

How the coverage is calculated
The plugin in charge of the test coverage calculation are Jacoco along with SonarCloud.
Jacoco it's executed during each build and produces a report inside the targe

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

In particular httpoutput uses httplib which relies on urllib and only supports HTTP/1.0 which causes problems in some setups.

Better is to use the requests package, also has a simpler programming model.