Arsh Sharma

Thanks. So here's the process that I can think of for my case: - We create a gitlab deploy token - We store the secrets as gitlab ci environment variables...

Based in the repro by @fredrikekre, this seems to have been fixed. I haven't been able to reproduce this?  Julia 1.6 Documenter v0.26.3

So the above GeoJSONTables solution works well for a list of Features(meta-geometries). Currently, what all can we have? * A Feature(meta-geometry struct that has properties and geometries together) * A...

It is breaking indeed. We are moving from something like `PointMeta` to `Meta{Point}`. This is to solve #49.

Yeah! The above method works. We have done a similar working implementation [here](https://github.com/JuliaGeo/Shapefile.jl/blob/sd/geometrybasics/src/table.jl#L22-L27). There's one problem with this approach. We actually construct the geometries initially(the `Base.read()` methods in [Shapefile.jl file](https://github.com/JuliaGeo/Shapefile.jl/blob/sd/geometrybasics/src/Shapefile.jl#L129-L307))...

@piever suggests that automatically widening for custom types seemed tricky while Nesting / unnesting on the fly is much easier. ```julia using GeometryBasics, StructArrays function maketable(iter) unnested_iter = Base.Generator(iter) do...

Now that things are getting a bit clear, we have come up with a different approach for handling meta and are slowly working towards it. Also experimenting with StructArrays along...

```julia julia> Polygon([Point(1,2), Point(5,6)]) isa GB.AbstractGeometry true julia> Point(1, 2) isa GeometryBasics.AbstractGeometry false ```

I now realize this is not realted to morphing. But `anim_translate` might be broken. ```julia star_obj = Object(1:60, astar) act!(star_obj, Action(30:40, anim_translate(Point(100, -100)))) act!(star_obj, Action(45:55, anim_translate(Point(100, -100)))) ``` So by...

So this is expected behaviour?