lnd/lnrpc/signrpc/config_default.go

//go:build !signrpc
// +build !signrpc

package signrpc

// Config is empty for non-signrpc builds.
type Config struct{}
multi: add golang 1.17 compatible build tags With go 1.17 a change to the build flags was implemented: https://go.googlesource.com/proposal/+/master/design/draft-gobuild.md The formatter now automatically adds the forward-compatible build tag format and the linter checks for them, so we need to include them in our code. 2021-08-23 10:35:48 +02:00			`//go:build !signrpc`
lnrpc/signrpc: add lnrpc.SubServerDriver for signrpc In this commit, we create a lnrpc.SubServerDriver for signrpc. Note that this file will only have its init() method executed if the proper build flag is on. As a result, only if the build flag is set, will the RPC server be registered, and visible at the packge lnrpc level for the root server to manipulate. 2018-10-23 02:41:14 +02:00			`// +build !signrpc`
lnrpc/signrpc: create new signrpc package with build-flag guarded config In this commit, we introduce a new sub-package within the greater RPC package. This new sub-package will house a new set of sub-RPC servers to expose experimental features behind build flags for upstream consumers. In this commit, we add the first config for the service, which will simply expose the lnwallet.Signer interface over RPC. In the default file, we have what the config will be if the build tag (signerrpc) is off. In this case, the config parser won't detect any times, and if specified will error out. In the active file, we have the true config that the server will use. With this new set up, we'll exploit these build flags heavily in order to create a generalized framework for adding additional sub RPC servers. 2018-10-23 02:28:12 +02:00
			`package signrpc`

lnrpc/signrpc: add lnrpc.SubServerDriver for signrpc In this commit, we create a lnrpc.SubServerDriver for signrpc. Note that this file will only have its init() method executed if the proper build flag is on. As a result, only if the build flag is set, will the RPC server be registered, and visible at the packge lnrpc level for the root server to manipulate. 2018-10-23 02:41:14 +02:00			`// Config is empty for non-signrpc builds.`
lnrpc/signrpc: create new signrpc package with build-flag guarded config In this commit, we introduce a new sub-package within the greater RPC package. This new sub-package will house a new set of sub-RPC servers to expose experimental features behind build flags for upstream consumers. In this commit, we add the first config for the service, which will simply expose the lnwallet.Signer interface over RPC. In the default file, we have what the config will be if the build tag (signerrpc) is off. In this case, the config parser won't detect any times, and if specified will error out. In the active file, we have the true config that the server will use. With this new set up, we'll exploit these build flags heavily in order to create a generalized framework for adding additional sub RPC servers. 2018-10-23 02:28:12 +02:00			`type Config struct{}`