Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update to use YamlDotNet nuget package

See original GitHub issue

I’m currently going through package dependencies of Elsa so we can get our commercial team to approve usage. I noticed that Elsa.Core uses package YamlDotNet.NetStandard 4.0.0. This has been unlisted and doesn’t have a link to licence information. Is it possible to switch over to YamlDotNet which looks like it’s from the same author, but does include licence info? I’m happy to make the change if you think it’s ok @sfmskywalker.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

sfmskywalkercommented, Jan 15, 2020

I’m glad you could fix it. Thanks a lot!

1reaction

jamesdorancommented, Jan 15, 2020

Thanks so much for looking into it, that’ll save me a heap of time 😃

On Wed, 15 Jan 2020 at 8:23 am, Sipke Schoorstra notifications@github.com wrote:

That’s amazing, thank you. I just had a quick glance at the YamlTokenFormatter, and I think it’s a simple matter of specifying a properly-configured JsonSerializerSettings object as is done in JsonTokenFormatter. It would probably exactly the same settings, but with an additional ExpandoObjectConverter added to the Converters collection of the settings.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/elsa-workflows/elsa-core/issues/225?email_source=notifications&email_token=AAIOBZR5MYUWKBCLBPKF6DLQ5YX4FA5CNFSM4KGNMYM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6IJ7A#issuecomment-574391548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIOBZRGMNAZG74N57EABOTQ5YX4FANCNFSM4KGNMYMQ .