Originally posted on StackOverflow.

The following code crashes with StackOverflowError and the stacktrace shows a long chain of request calls.

import io.reactivex.rxjava3.core.Flowable
import io.reactivex.rxjava3.core.Single
import io.reactivex.rxj

Hi,

I'm looking for something like .prettierignore but on a global level, i don't want to copy that file to every new directory i make just to ignore 1 file extension which isn't supported anyway.

AFAIK this isn't supported right?

BTW the extension in this case is EJS which prettier thinks is JS and some other stuff so the best way really is to ignore .ejs as a whole.

Type of issue: (feature suggestion, bug?)

Suggestion

Chapter:

no-chapter

Why use .jsx instead of .js? It's not a best practice: facebook/create-react-app#87 (comment)

There is some noise, I need to clean it up

When there are several encrypted scripts on the site, each one contains functions rc4(), base64(), md5().
If you added the disable include option for these functions in the CLI, I could add them only to the first script.

Do you want to request a feature or report a bug?
A bug
What is the current behavior?
Within container, It wants to look for cache in home directory though --cacheDir is given.

warning package.json: No license field
$ flow-typed install [email protected] [email protected] [email protected] --cacheDir /tmp/.cache/.flow-typed
• Searching for 3 libdefs...
• flow-typed cache not found, fetc

Motivation

Some IDEs like IntelliJ don't display the javadoc custom tags at all in their javadoc popup.

As a consequence, discovering information about the discard and continue support might be difficult.

Searching the HTML version or the source to look for information about support might still be acceptable, but the tags should not be the only places where eg. a caveat or structuring im

It was not immediately obvious to me how I should reference types generated by codegen throughout my application.

When creating multiple queries that access different fields on a schema type, this can cause issues for fields required on the schema type, but missing in the query.

The documentation loosely shows how to destructure a query result to use the inner objects, rather than using the

Document all supported URL patterns for elastic and other configuration variables. Allow users to validate a head if URL parameters in configuration stand in the supported patterns.

Examples:

http://hostname
http://hostname:port
http://IP:port
https://IP:port
IP:port
hostname

.... I probably missed some supported patterns ...

Flow supports contravariance (-), TypeScript doesn't.

Also, TypeScript doesn't support covariance (+) on all its types, but just some of them.

If you present a UIViewController and from that screen you make a step which change flow will create a memory leak by holding the NavigationController with full stack of ViewController within it. That flow is deallocated but the navigation controller and other view controller still exists on memory.

Hello!

I'd love to start contributing to this project but unfortunately I can't even seem to get it installed :(

I think maybe the best way I can start helping out is by improving the documentation! I would love to add in some extra info and different problems people might encounter.

I will post issues here so they can be answered individually, but I was wondering if it would be possible

Ideas:

• Set a minimum dimension for images.
• Find a way to detect dimensions before downloading the image.

const {links, history} = this.props

Expected: No error.

Actual: ESlint: missing variable type annotation. (flowtype-/require-variable-type)

Maybe I'm missing something, but I can't figure out a valid configuration for this case

"flowtype/require-variable-type": [
  2,
  {
    "excludeVariableMatch": "^map", // mapStateToProps & mapDispatchT

We should add some links to Prisma examples in the README & docs.

Describe the bug
Installation instructions in README.md file and on the Download and installation web page are outdated. Missing coverage for autogen.sh script.

To Reproduce
Steps to reproduce the behavior:

1. GIT Clone fresh Master source in a new empty folder
2. Attempt to execute ./configure per installation instructi

We have quite a few common booleans we use in many places of the code.
Some of them are very simple, like checking for compressible vs incompressible, or for FSI.
But when we want to express something more complicated like is it SA or SST, is the mesh moving or deforming, is this FEM or FVM or FEA, and so on, things are not so simple anymore and we end up with long conditionals repeated in many

@page has special rules here: https://developer.mozilla.org/en-US/docs/Web/CSS/@page

This is similar to @viewport which already has a custom type Viewport.

export interface Viewport<TLength = string | 0> {
  msHeight?: ViewportHeightProperty<TLength>;
  msMaxHeight?: ViewportMaxHeightProperty<TLength>;
  msMaxWidth?: ViewportMaxWidthProperty<TLength>;
  msMaxZoom?: ViewportMax