Hello,

Could you add the pop-up documentation of a function/variable when we press Ctrl + Q? For now it shows No documentation found. even if I used @doc on the function.

Thanks

I like yoda for 3 === $foo (instead of $foo === 3), but I don't like yoda for 3 === \my_method().

The main reasons for yoda is to avoid accidental assignments which can not happen on method calls.

Is it possible to either only suggest yodo for variable comparisons or to make it configurable in which cases it is suggested?

Here a some of the documentation tags JavaDoc uses. I'd like to have them available for Lua as well.

• {@code} = {@code sum = x + y}
• {@docRoot} = <a href="_{@docRoot}_/copyright.html">
• {@link class#member label} = Use the {@link #getComponentAt(int, int) getComponentAt} method > Use the getComponentAt method.
• `{@linkplain class#member lab

I believe our current error analytics include all the runtime errors the Flutter framework reports to the IDE. However, a substantial amount of those errors are likely to be triggered by the primary error the user really needs to deal with in their own code (e.g., flutter/flutter-intellij#4447). Can we log the primary error only, perhaps using the same logic from the PR men

Repro: go .cabal file, type quick somewhere in build-depends stanza, a suggestion list appears
Expected: the QuickCheck package is present in the suggestions' list
Instead: the QuickCheck package is absent in the suggestions' list

Eleventy is a static site generator. It uses .eleventyignore files to exclude files from the internal build process:

https://www.11ty.io/docs/ignores/

AFAIK globs are processed by fast-glob.

Would be nice if the server edit button would also be available in the tool window tool bar, so you can get to the edit dialogue without needing to use the context menu.

This plugin is confused because .lando.yml files may contain a top-level key services:. It says "Missing argument", when in fact all is fine.

These files are not meant for Symfony at all. For example, in the Drupal 8 ecosystem, both Lando and Symfony can coexist without any problems.

For documentation, see https://docs.devwithlando.io.

Using the HTML export option is it possible to save to a folder outside the project directory?

We use a different git repo for documentation but cant seem to get export to work if the folder structure is set outside the project.

Export Works
Parent Dir : E\myProject\docs
Target Dir : E\myProject\docs

No export
Parent Dir : E\myProject\docs
Target Dir : E\myDocst\docs

No export

Currently, we can only choose a background color.
I would be great if we can choose font and size also.
AceJump uses edit font family and font size, which sometimes make aceJump's popups barely visible.

Example below:

FLUP from #334

Currently, clicking edit on a configuration opens a dialog where you can change variables.
It'd be nice to be able to edit the name / file path too.

Right now I'd like to be able to change function name and class names colors. Because my Monokai theme makes the solidity file look very bland. Only 2-3 colors are used and makes coding difficult because I've spent years on Monokai in other languages.

With 2019.2 EAP

java.lang.Throwable: Synchronous execution under ReadAction: /usr/bin/info -w ifnames
	at com.intellij.openapi.diagnostic.Logger.error(Logger.java:145)
	at com.intellij.execution.process.OSProcessHandler.checkEdtAndReadAction(OSProcessHandler.java:117)
	at com.intellij.execution.process.OSProcessHandler.waitFor(OSProcessHandler.java:62)
	at com.intellij.execution.process.

Example:
I have a project that contains 3 sections - frontend, admin, api
Controllers and related code are placed in separate subfolders inside app folder:
frontend: \App\Http\Controllers
admin: \App\Admin\Http\Controllers
api: \App\Api\Http\Controllers
In my routes I declare this paths via 'namespace' and use short declaration of actions like 'DataController@action'.
What I would like to

Right now dot command is required for scabbard to be useful. We could build a validation step in Gradle plugin that checks for availability of dot and fails the build. Additionally providing commands to install dot in messages would be nice.

Problem

When manually entering additional bazel flags which contain quotes, the plugin changes the format.

Setup:

Result:

--test_filter=my.app.AppSpec "--test_arg=-testName \"Name of my spec\"" 

Other example:

--test_arg=-testName="Name of my spec"