Radu Gidei

subscribing to this as we're still using reflection for now.

I'd argue against that @arif-hanif as that sounds like a side-effect, think it would be better to have alignment as separate functionality where it makes sense

quick question here : should we consider making the return of this method `IEnumerable` ? reasons to consider it : - would fit nicely with how we're structuring some of...

Reading the release notes (see #140), this looks like it's been stealthily [implemented](https://github.com/hypar-io/elements/blob/master/CHANGELOG.md#added-2) in `0.2.1`, perhaps issue can be closed if so ?

+1 for things like `Vector3.IsHorizontal()` & `Vector3.IsVertical()` To help illustrate, we have a scenario where we want to taper a whole building, so we modify the top face & offset...

related to #117 , use-case is the same : rendering site boundary line (affectionately know as `the red line` 🤓 ) instead of adding a bool `renderProfiles` as a parameter...

@markthorley > In regards to lofting, ideally we would need both cases. We eventually would also need to handle lofts between two completely different shapes, maybe a rectangle and a...

I would chime in and say we would need the functionality prioritised in this order : - [ ] loft between two polygons with same count of segments & aligned...

That's the kind of thing that had inspired the original question btw 😁

is this the point when we consider an API gateway to handle this stuff (auth, rate, etc) ?