-
Notifications
You must be signed in to change notification settings - Fork 692
comitia:0.1.0 #3024
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
base: main
Are you sure you want to change the base?
comitia:0.1.0 #3024
Conversation
…e, prefer the field.
Smooth experience until now. Are the workflow checks available for deploying in other repositories without deploying half of the package repo? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this package! I've left a few comments regarding the readme and the included example.pdf
file.
Then you can either analyze the raw output using the function: | ||
|
||
```typst | ||
#vote(input, method: "STV", ties_method: "Random") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't compile, the second argument should be tie-method
Or you can have a more sophisticated report on each step performed: | ||
|
||
```typst | ||
#vote-report(input, method: "STV", ties_method: "Random") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here
|
||
Use different voting mechanisms in your document. Powered by Rust WASM. | ||
|
||
You can analyze a vote turnout by calling `vote(ballots, method, ties_method)` which returns the raw JSON results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The result doesn't seem to be a JSON string anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file will be very hard to find, unless someone is browsing this repository. Could you either remove it or link to it from the readme?
Regarding the package-check, you could run the CLI inside github actions. You could probably also somehow configure the github action runner in some way, though I didn't set that up so I'm not sure :) As for the bundler I think the package structure of this repository is currently hard coded. |
Thank you for your feedback. Will perform the changes probably within the next days. |
I am submitting
Description: Experiment with different voting mechanisms and tie-methods in your document.
I have read and followed the submission guidelines and, in particular, I
typst.toml
file with all required keysREADME.md
with documentation for my packageLICENSE
file or linked one in myREADME.md
exclude
d PDFs or README images, if any, but not the LICENSE