Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Error messaging in admiral: review & rework #2301

Closed
manciniedoardo opened this issue Jan 19, 2024 · 6 comments
Closed

Error messaging in admiral: review & rework #2301

manciniedoardo opened this issue Jan 19, 2024 · 6 comments
Assignees

Comments

@manciniedoardo
Copy link
Collaborator

manciniedoardo commented Jan 19, 2024

Background Information

From our 2024 roadmap call, @bundfussr made great points about some of the limitations of our error messaging in admiral - e.g. errors thrown when required variables are missing from dataset/dataset_add don't indicate in which dataset they are missing. We should carry out a review across our admiral functions, exploring where error messaging can be improved in terms of: verboseness and detail.

Improvement of our error messaging would be a great enhancement to the admiral experience with minimal (no?) breaking changes, perfectly embodying our admiral post-1.0 ethos.

Definition of Done

  • Review of error messages across admiral functions (focus on key ones first) to identify any gaps/confusion. Perhaps with a document outlining all the potential improvements? This document could then be reviewed by the team in order to decide on an action plan.
  • Issues created to improve error messaging.
@manciniedoardo
Copy link
Collaborator Author

@bundfussr I have assigned you to this issue as this was originally your suggestion - feel free to proceed with this if you like, or unassign yourself if you would not. I also think more than one person can be involved.

@manciniedoardo
Copy link
Collaborator Author

Potential idea: can we get a console message when users are using superseded functions?

@bms63
Copy link
Collaborator

bms63 commented Jan 19, 2024

Potential idea: can we get a console message when users are using superseded functions?

I feel like this should be a separate issue from the error/warning to users.

@bundfussr I have assigned you to this issue as this was originally your suggestion - feel free to proceed with this if you like, or unassign yourself if you would not. I also think more than one person can be involved.

I think this should be done in a breakout group with some more in-depth discussion. As this will need some investigation as well as thoughtful discussion.

@manciniedoardo
Copy link
Collaborator Author

I think this should be done in a breakout group with some more in-depth discussion. As this will need some investigation as well as thoughtful discussion.

Agree - honestly by initially assigning @bundfussr I was hoping that you could produce a review document, like the one for the function reword effort, that could form the basis of the work of such a group! It was so helpful that maybe we could replicate this modus operandi.

@bms63
Copy link
Collaborator

bms63 commented Jan 24, 2024

@bms63
Copy link
Collaborator

bms63 commented Feb 2, 2024

I'm going to move this to a Discussion as this is a large issue that needs to be broken into smaller chunks to tackle. Daniel has a presentation for us on Wednesday to help orient us from another project?? @ddsjoberg

https://www.danieldsjoberg.com/ARD-onboarding/05-cli-conditions.html

@pharmaverse pharmaverse locked and limited conversation to collaborators Feb 2, 2024
@bms63 bms63 converted this issue into discussion #2318 Feb 2, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Development

No branches or pull requests

4 participants