Feature/grpc multipackage

[AlexDaSoul]

before:

grpcOptions: <GrpcOptions>{
    transport: Transport.GRPC,
    options: {
        url: 'url',
        package: 'name.package',
        protoPath: 'alone.proto'
    }
}

after:

grpcOptions: <GrpcOptions>{
    transport: Transport.GRPC,
    options: {
        url: 'url',
        package: ['name.package', 'other.package'],
        protoPath: [
        'one.proto',
        'two.proto',
        'any.proto'
        ]
    }
}

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Added use packages and protos from external libraries ang default grpc functionality also https://github.com/grpc/grpc/blob/master/src/proto/grpc/health/v1/health.proto

grpcOptions: <GrpcOptions>{
    transport: Transport.GRPC,
    options: {
        url: 'url',
        package: ['name.package', 'grpc'],
        protoPath: [ 'name.proto', 'health.proto'],
        loader: {
            includeDirs: ['project', 'grpc/health/v1']
        }
    }
}

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Discussion #1733 (comment)

[coveralls]

Pull Request Test Coverage Report for Build 3622

• 20 of 20 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.005%) to 95.12%

---

Totals
Change from base Build 3491:	0.005%
Covered Lines:	4347
Relevant Lines:	4570

---

💛 - Coveralls

[marcus-sa]

Could you add support for globbing using e.g https://github.com/micromatch/micromatch?

If it's out of the scope, I'll just create a PR after this is merged.

Since you can't define protos to load at module level, then this would be a handy feature.

[AlexDaSoul]

Could you add support for globbing using e.g https://github.com/micromatch/micromatch?

If it's out of the scope, I'll just create a PR after this is merged.

Since you can't define protos to load at module level, then this would be a handy feature.

It's out of the scope but you can add issue and we discuss this

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.