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.

Sign up for GitHub

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

Jump to bottom

Add hazards #6

Open
TheAsel opened this issue Oct 31, 2023 · 1 comment
Open

Add hazards #6

TheAsel opened this issue Oct 31, 2023 · 1 comment
Assignees
@TheAsel
Labels
backend Needs backend support encounter Related to the Encounter Builder enhancement New feature or request question Further information is requested

Comments

@TheAsel
Copy link
Owner

TheAsel commented Oct 31, 2023

Could be interesting to also include hazards into the mix. Might me out of scope and could be hard to fit into the existing table due to different columns (e.g., complexity, hazard type)
@TheAsel TheAsel added enhancement New feature or request encounter Related to the Encounter Builder backend Needs backend support labels Oct 31, 2023
@TheAsel TheAsel self-assigned this Oct 31, 2023
@RakuJa
Copy link
Collaborator

RakuJa commented Nov 5, 2023

I think this could be only done by having a sort of checkbox like
[x] Hazard
And then the backend will return strings representing the hazard, stored in the be database without being reflected in the frontend table

@TheAsel TheAsel added the question Further information is requested label Dec 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TheAsel TheAsel

Labels
backend Needs backend support encounter Related to the Encounter Builder enhancement New feature or request question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RakuJa @TheAsel