🎉 Hackathon - Preflight Checks Maker Fair✨

Hi everyone,

As mentioned in our previous meetup, we are launching:

Hackathon around the Preflight Checks feature.

Details can be found here:
Hackathon - Preflight Checks - Conditions

after reading all the details, if you still have questions:


Deadline is November 1st, 2024


Categories & Prizes

All relevant entries will be added to the official pyRevit preflight checks.

  • :star_struck: Keep It Simple - $25 Gift Card or Equivalent
    A check that is both simple and smart.
  • :computer: Code Elegance - $50 Gift Card or Equivalent
    Code that is either artistically elegant or highly Pythonic.
  • :rocket: Most Advanced - $100 Gift Card or Equivalent
    A complete check that pushes the boundaries of quality control.
  • :astronaut::computer::star: Best of the Best - $200 Gift Card or Equivalent
    Simple, elegant, advanced, and maybe even smarter than the others—this entry might include a library that makes the check more reusable. Code improvements to the Preflight Checks Tools are also welcome.

and some extra references: preflights checks in pyRevit documentation

7 Likes

I want to say that I feel actually excited. a very strange feeling indeed.
I’ll do my best to contribute to this effort.

1 Like

Nice initiative! :tada:

Would it be possible to include check-scripts located in custom extensions?
I.e. placing a checks folder in the extension, like we do with hooks now.

I tried to find a way to iterate over the extensions and add scripts in a “checks” folder in lib or extension root, but I have limited understanding of the pyrevit master code.

It would be great for those that develop company specific QA/checks, and woukd make it easier to develop new checks to be added to pyRevit, since we dont have to change/add to the main pyrevit repo code.

this is already implemented (from day one)
in your custom.extension folder you just have to add your folder named checks and put your script.py in here.

1 Like

Thats what I get for overcomplicate things…

Thank you for explaining :+1:

quoting myself in the docs: preflight checks documentation

The ‘checks’ are all located in a ‘checks’ folder at the root of any extension folder (meaning even in a custom extension folder). The basic ones that comes with pyRevit as well: