Added Toml types from SEP1

[tobinbc]

#371

Added all the fields I could find in SEP1; and other sources when building my Anchor.

They are not readonly because if going in the other direction it can be desired to assemble the object first before it is tomlified.

Is there any desire to bring in the reverse?
e.g.

const TOML = require("@iarna/toml");
const body = TOML.stringify(config);

[JakeUrban]

This is great @tobinbc, thanks for contributing this.

About generating the TOML content from a StellarTomlResolver.StellarToml object, I think it would be helpful, but wouldn't that functionality be best implemented in the toml library? The toml library in the Python ecosystem has a .dumps() function that accepts an arbitrary dict and creates the TOML contents. I would assume the JavaScript variant has the same functionality for objects, but it doesn't look like it which is a bit surprising.

[Shaptic]

Nice add! We can add the reverse direction if there's need later.

[tobinbc]

Awesome thanks! Yeah no worries. It does make sense to just use the types and provide your own toml converter.

…

On Tue, 4 Oct 2022 at 18:54, George ***@***.***> wrote: ***@***.**** approved this pull request. Nice add! We can add the reverse direction if there's need later. — Reply to this email directly, view it on GitHub <#794 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEMR55URNNU7E3DYGZMNBHDWBRVOLANCNFSM6AAAAAAQXDAOMU> . You are receiving this because you were mentioned.Message ID: ***@***.***>