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

create table with question types #673

Merged
merged 2 commits into from
Jul 26, 2023
Merged

create table with question types #673

merged 2 commits into from
Jul 26, 2023

Conversation

jreidinger
Copy link
Contributor

Problem

Answers file supports various questions, but there is no central place for list of current questions and its answers.

Solution

Document it.

doc/questions.md Outdated

| class | description | possible answers | available data | notes |
|--- |--- |--- |--- |--- |
| software.medium\_error | When there is issue with access to medium | `Retry` `Skip` | `url` with url where failed access happen | |
Copy link
Contributor

Choose a reason for hiding this comment

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

With this style it will be easier to keep the docs up to date in case we ever rename a class and grep for it in the repo.

Suggested change
| software.medium\_error | When there is issue with access to medium | `Retry` `Skip` | `url` with url where failed access happen | |
| `software.medium_error` | When there is issue with access to medium | `Retry` `Skip` | `url` with url where failed access happen | |

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah, makes sense

Copy link
Contributor

@joseivanlopez joseivanlopez left a comment

Choose a reason for hiding this comment

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

About inconsistency with the answers, originally the idea was to have some kind of key for each possible answer: "yes", "no", "maybe", etc. And the clients are responsible of presenting a readable text to the user, for example:

yes -> Accept
no -> Cancel
maybe -> Decide later

I guess software has capitalize answers because the web client is directly using the answers as text. IMHO, I would avoid that.

@coveralls
Copy link

Coverage Status

coverage: 72.172%. remained the same when pulling c47724c on doc_question_types into 5d4f3b2 on master.

@jreidinger jreidinger marked this pull request as ready for review July 26, 2023 13:04
@jreidinger jreidinger merged commit d0ac7f2 into master Jul 26, 2023
14 checks passed
@jreidinger jreidinger deleted the doc_question_types branch July 26, 2023 13:05
@imobachgs imobachgs mentioned this pull request Aug 2, 2023
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.

4 participants