mirror of
https://github.com/jesseduffield/lazygit.git
synced 2024-12-14 11:23:09 +02:00
e33fe37a99
We've been sometimes using lo and sometimes using my slices package, and we need to pick one for consistency. Lo is more extensive and better maintained so we're going with that. My slices package was a superset of go's own slices package so in some places I've just used the official one (the methods were just wrappers anyway). I've also moved the remaining methods into the utils package.
18 lines
514 B
Go
18 lines
514 B
Go
package presentation
|
|
|
|
import (
|
|
"github.com/jesseduffield/lazygit/pkg/commands/models"
|
|
"github.com/jesseduffield/lazygit/pkg/theme"
|
|
"github.com/samber/lo"
|
|
)
|
|
|
|
func GetSubmoduleListDisplayStrings(submodules []*models.SubmoduleConfig) [][]string {
|
|
return lo.Map(submodules, func(submodule *models.SubmoduleConfig, _ int) []string {
|
|
return getSubmoduleDisplayStrings(submodule)
|
|
})
|
|
}
|
|
|
|
func getSubmoduleDisplayStrings(s *models.SubmoduleConfig) []string {
|
|
return []string{theme.DefaultTextColor.Sprint(s.Name)}
|
|
}
|