Skip to content
Discussion options

You must be logged in to vote

This issue should now be fixed in version 1.2.0. Please give it a try. Thanks!

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@DarioSantoro81
Comment options

@electroly
Comment options

Answer selected by electroly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants