`stack query locals` does not distinguish extra deps

[mitchellwrosen]

Running stack query locals does not indicate which local packages are actually extra deps. This would be very valuable information to have! Thanks.

[kartik-sabharwal]

I would like to understand the issue a little better.

As of now when I run stack query locals in a stack project a list of
yaml key-value pairs is printed out. Each item in the list corresponds to
a local package listed under packages in the project's stack.yaml file.
Local packages listed under extra-deps in the stack.yaml file aren't
mentioned in the list generated by stack query locals. You're saying that
the extra deps should appear in this list, correct? If they should then are
they to be differentiated from the other local packages that aren't extra deps?

As an example, consider the following lines in a stack.yaml file of a
project called greek:

    ...
    ...
    packages:
    - .
    - alpha

    extra-deps:
    - beta
    - gamma
    ...
    ...

Currently when I run stack query locals in this project I see
text like:

    alpha:
      path: {concealed for privacy}/greek/alpha/
      version: '0.1.0.0'
    greek:
      path: {concealed for privacy}/greek/
      version: '0.1.0.0'

But after the necessary change I should get output like

    alpha:
      path: {concealed for privacy}/greek/alpha/
      version: '0.1.0.0'
    beta:
      path: {concealed for privacy}/greek/beta/
      version: '0.1.0.0'
    gamma:
      path: {concealed for privacy}/greek/gamma/
      version: '0.1.0.0'
    greek:
      path: {concealed for privacy}/greek/
      version: '0.1.0.0'

Right?