Expose DOT-specific keywords

[0xmichalis]

A user shouldn't manually construct DOT keywords before adding them in the attributes of a graph object. All the names mentioned in here should be exposed by this package.

[awalterschulze]

I agree, it would be safer to have all the attributes so stringly typed.

We could make type safe and constrained methods to build the map[string]string and not break the current API.

This is quite a long list of things to implement and, unfortunately, I am currently very busy, but I would be open to contribution.
I am very sorry and I hope that this is an acceptable answer?

[0xmichalis]

Thanks for the answer! No worries, it's good that you agree about the issue. I might submit a PR if time permits it.:)

[awalterschulze]

I look forward to it :)

On 20 March 2015 at 12:30, Michail Kargakis [email protected]
wrote:

Thanks for the answer! No worries, it's good that you agree about the
issue. I might submit a PR if time permits it.:)

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

[awalterschulze]

I have decided that we are going to make a breaking change to return some errors.
Or at least that is what this proposal is about
#23
Hopefully we can then fix this keyword problem as well.

[awalterschulze]

Merged pull request #25 with some attribute validation.