Skip to content
Discussion options

You must be logged in to vote

This was actually a bug but is has now been fixed. The fix will be included in v0.13 which is expected to be released this week.

Replies: 1 comment 2 replies

Comment options

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

@mdecimus
Comment options

Answer selected by HeWhoWatches
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