Wanted: Sane API that Corresponds to Interface Actions

asher_haig

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?

asher_haig

And why can't we name sketches? That's so far beyond insane I can't even comprehend it. It undermines all basis for organization.

Paul_J_Premakumar

@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

asher_haig

How can it be done in Featurescript rather than via an external URL call?

I'm looking for something sane like:

var sketch = newSketchOnPlane(context, sketch_id, {
    "Name" : "Neck Relief Sketch",
    "sketchPlane" : plane
});
sketch.name = "Neck Relief Sketch";

Also, why doesn't it simply use the already provided "Name" parameter? This seems so basic.