Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config validation on programmatic start #435

Merged
merged 9 commits into from
Jul 1, 2019
Merged

Config validation on programmatic start #435

merged 9 commits into from
Jul 1, 2019

Conversation

kvosper
Copy link
Contributor

@kvosper kvosper commented Jun 14, 2019

Have config validation take place when StyxServer is created programmatically, e.g. for tests.

@kvosper kvosper requested review from dvlato and mikkokar and removed request for dvlato June 14, 2019 14:11
Copy link
Contributor

@mikkokar mikkokar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's avoid adding new classes unless absolutely necessary.

Kotlin tests already provide exception matchers out of box. No need to implement them.

The laziness seems a premature optimisation which also adds bloat to the code. I would encourage removing that. Unless I am missing something?

@kvosper kvosper merged commit 517b649 into ExpediaGroup:master Jul 1, 2019
@kvosper kvosper deleted the config-validation-on-programmatic-start branch July 1, 2019 12:37
dvlato pushed a commit that referenced this pull request Jul 3, 2019
Validate config when StyxServer is started programmatically
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants