Best Of

@NeilCooke it's uBlock Origin Lite. Thanks for clearing that up.

@asher_haig , And why can't we name sketches? : Can you let us know what you tried? You should be able to set the name of the sketch at creation see this example : https://onshape-public.github.io/docs/api-adv/featureaccess/#create-a-sketch-via-querystring or if you want to update the name of a sketch (or any other feature) see this example : https://onshape-public.github.io/docs/api-adv/featureaccess/#update-a-feature

• Create folders that would maybe result in a dropdown. I could have a "Gears" folder with planetary gears feature and the spur gear feature living together in the pulldown.
  
• Have links next to or behind the menu item to display the documentations, if available.
• A place where I can find all the exsiting custom features in an overview, search them in a targeted manner and get a how-to and maybe a sample.
  

Why is this not an automatic assumed given?

Why is the norm for writing OnShape code that we are expected to re-implement the features already provided by the app but not provided to the API?

Why can't we construct sketches by describing their constraints, the same way we would in the app?

Why aren't products of code accessible as first-class objects?

It's offensive how silly the API is. Why isn't there a real API that works the intelligent way the app works?

… and please make it hierarchic in some kind of way, so users can sort their FS collection by subject. Like thread creation FS in one branch, laser cutting aid FS in another and so on. It is getting confusing pretty fast if the list is long, even when sorted by name, 'cause the name usually don't start with an overly desciptive character.