I am indeed getting a working result, but the result has to be read through TriangulationPoint type and it only contains X and Y, not the index of vertex. When polygon is first passed to triangulation the vertices were indexed in order, this information is simply lost now, and we are getting unique vertices per triangle corner. It is not great that the final result of the polygon has 3 times as many vertices than the original one.
Of course a workaround can be made to merge those that are in exact same coordinates but this is manual work for each one using this library.
I am indeed getting a working result, but the result has to be read through TriangulationPoint type and it only contains X and Y, not the index of vertex. When polygon is first passed to triangulation the vertices were indexed in order, this information is simply lost now, and we are getting unique vertices per triangle corner. It is not great that the final result of the polygon has 3 times as many vertices than the original one.
Of course a workaround can be made to merge those that are in exact same coordinates but this is manual work for each one using this library.