Skip to content

Conversation

@jnation3406
Copy link
Member

This is stuff Blanco requested, but I think it makes sense for everyone. Two changes:

  • Renaming the label for a RequestGroup name to Request Name from just Name - I guess it was confusing since some people thought it meant a persons name should go there.
  • When a target is entered and not visible, the error shows up at the Request level, and the Window section just doesn't show an Airmass Plot. This change is so that the error from the /airmass/ endpoint is incorporated into the Window section error, so if a target is not visible, the window visibility error should show up in the Window section and at the top of the Request.

@jnation3406 jnation3406 requested a review from jashan-lco August 20, 2025 06:24
computed: {
topLevelErrors: function() {
return extractTopLevelErrors(this.errors);
let combinedError = extractTopLevelErrors(this.errors);
Copy link
Member Author

Choose a reason for hiding this comment

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

this.errors comes from a prop passed down from the parent, and will have errors on specific fields. The airmassData can also have an error (if there is an error with visibility), in which case this code below should include that in the error list shown at the top of this component.

@jnation3406 jnation3406 merged commit 077bad5 into main Aug 26, 2025
15 checks passed
@jnation3406 jnation3406 deleted the fix/visibility_error branch August 26, 2025 22:42
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.

2 participants