Closed
Description
Feature is present in https://github.com/ms-jpq/chadtree (GIF there showing it in action).
Suppose you have a typical project file tree like:
.
├── Dockerfile
├── README.md
├── api
│ ├── bulk
│ │ └── endpoint.go
│ └── graph
│ ├── endpoint.go
│ ├── generated
│ │ └── generated.go
│ ├── model
│ │ ├── models.go
│ │ ├── models_gen.go
│ │ └── namespaces
│ │ └── namespaces.go
│ ├── resolver
│ │ ├── common.resolvers.go
│ │ ├── filters.resolvers.go
│ │ ├── resolver.go
│ │ └── schema
│ │ ├── common.graphql
│ │ └── filters.graphql
│ └── signing
│ ├── signing.go
│ └── signing_test.go
├── config
│ └── config.go
├── config.yaml
├── db
│ └── migrations
│ └── 0000_average_spend.up.sql
├── docker-compose.yaml
├── go.mod
├── go.sum
├── gqlgen.yml
├── kube
│ └── dev.yaml
├── main.go
├── services
│ ├── ingestion.go
│ └── services.go
├── storage
│ ├── dataset.go
│ ├── filters.go
│ ├── filters_test.go
│ └── postgres.go
├── terraform
│ ├── dev-postgres.tf
│ └── main.tf
└── util
├── log
│ └── log.go
└── types
└── decimal.go
and I want to see the tree of all the graphql files only via applying a filter *.graphql, I'd expect the tree to appear as
.
└── api
└── graph
└── resolver
└── schema
├── common.graphql
└── filters.graphql
Regardless if this is implemented or not, awesome project @kyazdani42, you're awesome!