Skip to content

Commit

Permalink
Restore camelCase key names
Browse files Browse the repository at this point in the history
Since the Viper patch has been absorbed into main, it's OK to use
camelCase in config files again.

Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
  • Loading branch information
awrichar committed Aug 19, 2022
1 parent 9914795 commit 7d9ad40
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 4 deletions.
1 change: 0 additions & 1 deletion internal/stacks/stack_manager.go
Original file line number Diff line number Diff line change
Expand Up @@ -837,7 +837,6 @@ func (s *StackManager) runFirstTimeSetup(options *types.StartOptions) (messages
Predefined: []*types.Namespace{
{
Name: "default",
RemoteName: "default",
Description: "Default predefined namespace",
Plugins: []string{"database0", "blockchain0"},
},
Expand Down
5 changes: 2 additions & 3 deletions pkg/types/namespace.go
Original file line number Diff line number Diff line change
Expand Up @@ -18,11 +18,10 @@ package types

type Namespace struct {
Name string `yaml:"name"`
RemoteName string `yaml:"remotename,omitempty"`
Description string `yaml:"description,omitempty"`
Plugins []string `yaml:"plugins"`
Multiparty *MultipartyConfig `yaml:"multiparty,omitempty"`
DefaultKey interface{} `yaml:"defaultkey"`
DefaultKey interface{} `yaml:"defaultKey"`
}

type Plugins struct {
Expand All @@ -41,7 +40,7 @@ type MultipartyConfig struct {

type ContractConfig struct {
Location interface{} `yaml:"location"`
FirstEvent string `yaml:"firstevent"`
FirstEvent string `yaml:"firstEvent"`
}

type MultipartyOrgConfig struct {
Expand Down

0 comments on commit 7d9ad40

Please sign in to comment.