ClientConfigLoadingRules is an ExplicitPath and string slice of specific locations that are used for merging together a Config Callers can put the chain together however they want, but we'd recommend: EnvVarPathFiles if set (a list of files if set) OR the HomeDirectoryPath ExplicitPath is special, b
| 113 | // EnvVarPathFiles if set (a list of files if set) OR the HomeDirectoryPath |
| 114 | // ExplicitPath is special, because if a user specifically requests a certain file be used and error is reported if this file is not present |
| 115 | type ClientConfigLoadingRules struct { |
| 116 | ExplicitPath string |
| 117 | Precedence []string |
| 118 | |
| 119 | // MigrationRules is a map of destination files to source files. If a destination file is not present, then the source file is checked. |
| 120 | // If the source file is present, then it is copied to the destination file BEFORE any further loading happens. |
| 121 | MigrationRules map[string]string |
| 122 | |
| 123 | // DoNotResolvePaths indicates whether or not to resolve paths with respect to the originating files. This is phrased as a negative so |
| 124 | // that a default object that doesn't set this will usually get the behavior it wants. |
| 125 | DoNotResolvePaths bool |
| 126 | |
| 127 | // DefaultClientConfig is an optional field indicating what rules to use to calculate a default configuration. |
| 128 | // This should match the overrides passed in to ClientConfig loader. |
| 129 | DefaultClientConfig ClientConfig |
| 130 | } |
| 131 | |
| 132 | // ClientConfigLoadingRules implements the ClientConfigLoader interface. |
| 133 | var _ ClientConfigLoader = &ClientConfigLoadingRules{} |
nothing calls this directly
no outgoing calls
no test coverage detected