What example does this report relate to?

with-Apollo

What version of Next.js are you using?

10.0.0

What version of Node.js are you using?

10.14.2

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

Other platform

Describe the Bug

The Apollo client query response is s

This is a bug report of an edge case that can only happen if you have a hardhat project inside a monorepo, and the hardhat project is also an npm project p.

If a solidity file within p imports another one using import "p/contracts/...", the compilation will fail. The reason for this is that the file ends up with two source names p/contract/... and contracts/....

This only happens w

Currently the eldoc type is either function or variable:

(defn- extract-eldoc
  [info]
  (if-let [arglists (seq (-> info extract-arglists format-arglists))]
    {:eldoc arglists :type "function"}
    {:type "variable"}))

This means that the result users see is not particularly accurate, not to mention that the function check is pretty primitive. We should add types like `m

Feature Request

Feature Suggestion

This is working:

- Status: superseded by [20201016-use-the-adr-slug-as-its-unique-id](20201016-use-the-adr-slug-as-its-unique-id.md)

This is not working:

- Status: superseded by [custom name](20201016-use-the-adr-slug-as-its-unique-id.md)

-> Let's make it work!

Context

Today, the link name MUST b

The current error reporting screen supports both light and dark themes, using the Material Components library. It would be great if we could provide more customization options to the user in the form of additional themes.

Tasks:

• Add additional themes to styles.xml
• Make themes configurable through application code, or