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

Validation of input and checking for errors #35

Closed
5 tasks done
RiledUpCrow opened this issue Feb 6, 2015 · 2 comments
Closed
5 tasks done

Validation of input and checking for errors #35

RiledUpCrow opened this issue Feb 6, 2015 · 2 comments
Assignees
Milestone

Comments

@RiledUpCrow
Copy link
Contributor

Every condition, event and objective should have some form of validating instruction string. This would prevent errors from incorrect user input and display a helpful message.

There should be also a conversation structure validation upon reloading. This would check if there are some missing options, if every condition/event is defined and so on.

Effect of these checks should be logged to a file, so nothing gets undetected.

  • Conversation structure checking
  • Validating instruction strings in conditions
  • Validating instruction strings in events
  • Validating instruction strings in objectives
  • Validating item instructions
@RiledUpCrow RiledUpCrow self-assigned this Feb 6, 2015
@RiledUpCrow RiledUpCrow added this to the 1.6 version milestone Feb 6, 2015
@ghost
Copy link

ghost commented Feb 6, 2015

by this you could check the commands /q condition and /q event which run into an error when typing in a non-exsistent .

@RiledUpCrow
Copy link
Contributor Author

Yep, that check can also be implemented to commands.

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

No branches or pull requests

1 participant