AydarZaynutdinov commented on a change in pull request #15842:
URL: https://github.com/apache/beam/pull/15842#discussion_r740852132



##########
File path: playground/backend/internal/environment/application.go
##########
@@ -38,8 +38,13 @@ func (serverEnvs NetworkEnvs) Address() string {
 
 //CacheEnvs contains all environment variables that needed to use cache
 type CacheEnvs struct {
-       cacheType         string
-       address           string
+       // cacheType is type of cache (local/redis)
+       cacheType string
+
+       // address of where the cache is running

Review comment:
       Changed.

##########
File path: playground/backend/internal/environment/application.go
##########
@@ -69,8 +74,13 @@ func NewCacheEnvs(cacheType, cacheAddress string, 
cacheExpirationTime time.Durat
 
 //ApplicationEnvs contains all environment variables that needed to run 
backend processes
 type ApplicationEnvs struct {
-       workingDir             string
-       cacheEnvs              *CacheEnvs
+       // workingDir is a root working directory of application

Review comment:
       Changed.

##########
File path: playground/backend/internal/environment/application.go
##########
@@ -69,8 +74,13 @@ func NewCacheEnvs(cacheType, cacheAddress string, 
cacheExpirationTime time.Durat
 
 //ApplicationEnvs contains all environment variables that needed to run 
backend processes
 type ApplicationEnvs struct {
-       workingDir             string
-       cacheEnvs              *CacheEnvs
+       // workingDir is a root working directory of application
+       workingDir string
+
+       // cacheEnvs contains environments for cache

Review comment:
       No, we can have only one `cacheEnvs` which contains several `environment 
variables` (not several `environments`). Updated this comment.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to