feat: add base support for path text

[quarksb]

Resolve #168

[Agamnentzar]

Can you supply PSD file with some text on curves for tests

[quarksb]

I can't attach psd file due to github has limited the file type, so I will send it by email, please check your email

[Agamnentzar]

EngineData type only works for per-layer engine data field, it doesn't match the of the global engine data. This field doesn't exist: globalEngineData?.ResourceDict?.TextFrameSet. Insted the curve data is probably somewhere in globalEngineData.EngineDict['Editors?'][0]['FontVectorData ???']

[quarksb]

sorry for answer so lately, I was trapped by work last week.
I believe this field exist: globalEngineData?.ResourceDict?.TextFrameSet. but since ResourceDict is not an array but an object, so I shoud us Object.keys(ResourceDict).length instead of ResourceDict.length to figure out whether it's empty.

[Agamnentzar]

Hmm, ok, I didn't notice up updated some keys in engineData2.ts, can you change back spaces to tabs so the diff is correct. Also layer.effects field in layer is for blending effects, you should put curves into layer.text.curves instead. Also my comment about EngineData type still stands, instead you can create GlobalEngineData type for that data.

[quarksb]

can you give me your prettier config to help me change back spaces to tabs so the diff is correct, sorry to formmat this code

[Agamnentzar]

can you give me your prettier config to help me change back spaces to tabs so the diff is correct, sorry to formmat this code

I use default typescript formatting in vscode

[quarksb]

ok, I will perfect this pr later, since I have to do my job now

[quarksb]

I have update my pr, except GlobalEngineData, In my opinion, we can reuse EngineData, since there is no clear difference between GlobalEngineData and EngineData.
of course, you can change the code as you wish

[Agamnentzar]

I think the name field might not be labelled correctly

[Agamnentzar]

@quarksb Just released version 27.0.0 with support for layer.text.textPath field. I changed field names to lowercase to keep consistent with rest of the types and adjusted types a bit.

[quarksb]

could you give me more info about this?

I think the name field might not be labelled correctly

[Agamnentzar]

I can't find that anymore for some reason, maybe it was a fluke.