Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Make each component/module responsible for validation its configuration #3196

Closed
shuse2 opened this issue Mar 27, 2019 · 1 comment
Closed

Make each component/module responsible for validation its configuration #3196

shuse2 opened this issue Mar 27, 2019 · 1 comment
Assignees
@2snEM6
Labels
type: improvement
Milestone
Improve Lisk Fram...

Comments

@shuse2
Copy link
Collaborator

shuse2 commented Mar 27, 2019

Expected behavior

Each component and module should have own definition of the input, and validate according to the definition

Actual behavior

Currently, it's not validating

Parent

#3149

Which version(s) does this affect? (Environment, OS, etc...)

1.6-
@MaciejBaj MaciejBaj mentioned this issue Mar 27, 2019
Closed
14 tasks
@2snEM6
Copy link
Contributor

2snEM6 commented Apr 9, 2019

Closing. Implemented in feature/improve_overall_configuration branch.

@2snEM6 2snEM6 closed this as completed Apr 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@2snEM6 2snEM6

Labels
type: improvement
Projects
None yet
Milestone
Improve Lisk Framework UX - Phase 1
Development

No branches or pull requests
2 participants
@shuse2 @2snEM6