-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix empty directive name #140
base: develop
Are you sure you want to change the base?
Conversation
Presumably this would mean that a directive with |
@joshhaug My thought too. I'd like that we can preserve an empty name, and only a |
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.
Discussed with Brad. If an empty string is specified as a directive name, it can cause issues in the timeline in 2.12.
@cartermak just saw your comment but not sure I understand your question. It looks like there is an issue in 2.12 that causes |
Is this a bug or an expected behavior? If this is a bug, and an empty name should generally be acceptable, then I think Aerie-CLI should support it and I expect Aerie would resolve. If an empty name is not allowed, then I might argue for explicit handling of that case on the client side (e.g., report an error) instead of defaulting to a behavior like automatically assigning a name. |
Theresa's suggested fix for using the directive type also as the directive name when name is empty for plan uploads.