fixed the ci golint file exists

[captain-Akshay]

Description

This PR fixes #378
reference to github issue where the golangci-lint crew recommends this workaround: golangci/golangci-lint-action#244

Notes for Reviewers
This will increase the time complexity.
skip-pkg-cache: true
skip-build-cache: true
Signed commits

• Yes, I signed my commits.

[welcome]

Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack.
Be sure to double-check that you have signed your commits. Here are instructions for making signing an implicit activity while peforming a commit.

[captain-Akshay]

@theBeginner86 do let me know your review or feedback!
Thanks!

[leecalcote]

Running build checks...

[nebula-aac]

@captain-Akshay

Can you run golangci-lint run ./... --fix to fix the formatting issue and update this fork?

[captain-Akshay]

@nebula-aac got this error :-

& when i commented the unused variable the code golangci-lint run ./... --fix run fine!

[theBeginner86]

@nebula-aac got this error :-

& when i commented the unused variable the code golangci-lint run ./... --fix run fine!

Sounds good to me. Lets remove the un-used occurrences of var.

[captain-Akshay]

@theBeginner86 actually i checked the whole function and the komposeObject is being used in this file
and the only work around i was able to find was
changing this code:-

komposeObject := kobject.KomposeObject{
		ServiceConfigs: make(map[string]kobject.ServiceConfig),
	}

to

var komposeObject kobject.KomposeObject
komposeObject.ServiceConfigs = make(map[string]kobject.ServiceConfig)

now i might be wrong because I'm newbie in go 😅 but if you have something else do let me know !

this gives out no error while running golangci-lint run ./... --fix

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.