Skip to content

Conversation

pteridin
Copy link

@pteridin pteridin commented Sep 7, 2025

I am submitting

  • a new package
  • an update for a package

Description: Experiment with different voting mechanisms and tie-methods in your document.

I have read and followed the submission guidelines and, in particular, I

  • selected a name that isn't the most obvious or canonical name for what the package does
  • added a typst.toml file with all required keys
  • added a README.md with documentation for my package
  • have chosen a license and added a LICENSE file or linked one in my README.md
  • tested my package locally on my system and it worked
  • excluded PDFs or README images, if any, but not the LICENSE
  • ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

@typst-package-check typst-package-check bot changed the title comitia:0.1.0 typst-comitia:0.1.0 Sep 7, 2025
@typst-package-check typst-package-check bot added the new A new package submission. label Sep 7, 2025
@pteridin pteridin changed the title typst-comitia:0.1.0 comitia:0.1.0 Sep 7, 2025
@pteridin
Copy link
Author

pteridin commented Sep 7, 2025

Smooth experience until now.

Are the workflow checks available for deploying in other repositories without deploying half of the package repo?

Copy link
Member

@saecki saecki left a 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")
Copy link
Member

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")
Copy link
Member

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
Copy link
Member

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

Copy link
Member

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?

@saecki saecki self-assigned this Sep 8, 2025
@saecki
Copy link
Member

saecki commented Sep 8, 2025

Are the workflow checks available for deploying in other repositories without deploying half of the package repo?

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.

@pteridin
Copy link
Author

pteridin commented Sep 8, 2025

Thank you for your feedback. Will perform the changes probably within the next days.

@saecki saecki added the waiting-on-author Pull request waits on author label Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new A new package submission. waiting-on-author Pull request waits on author
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants