-
Notifications
You must be signed in to change notification settings - Fork 22
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
Rename InvalidArgumentsException
-> InstantiationException
#371
Conversation
692d807
to
80bb5fa
Compare
80bb5fa
to
98f70e7
Compare
47c8ca4
to
ac4f724
Compare
I feel like "erroneous" is still roughly synonymous; I could still see confusion arising here. How about |
Or, since the exception occurs directly on the |
Update aerielander.jar
ac4f724
to
6e382bf
Compare
|
InvalidArgumentsException
-> ErroneousArgumentsException
InvalidArgumentsException
-> InstantiationException
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
- Required after NASA-AMMOS/aerie#371
- Required after NASA-AMMOS/aerie#371
- Required after NASA-AMMOS/aerie#371
- Required after NASA-AMMOS/aerie#371
Description
Note: this PR's renaming changes the sig. of a mission model interface, therefore mission models must be updated.
This PR renames
InvalidArgumentsException
->InstantiationException
to minimize confusion between arguments being "invalid" (unconstructable, missing, or extraneous) and our "validation" endpoint responses indicating arguments that are "invalid" (failed an@Validation
check).Verification
All tests passing.
Documentation
Related docs updated.
Future work
None.