Remove the jmespath.net.interop project

[StefH]

My idea is to remove the jmespath.net.interop project and just move that single interface file into the Parser project.

[StefH]

@springcomp
Is this possible?

[springcomp]

Absolutely, that would also simplify the atrocious code in publish.yaml to handcraft the nuget package.

[StefH]

1]
OK

2]
What do you think about also just copying all code from Parser into the main project and also removing the Parser?

[springcomp]

The split between a generic parser and its current host using Newtonsoft.Json has been deliberate.
I think the change has been made in #26.
I think we should keep if for compatibility purposes, at least in spirit.
We can absolutely re-architect and even make breaking changes if necessary as long as a mitiation / migration path is documented.

What do you think?

[StefH]

Ah, now I understand a bit more about the jmespath.net.interop
In my idea, I would have created a normal project named jmespath.net.abstractions which defines that interface. (This pattern is also used by Microsoft)

--

The question is : will there be another Parser project? Maybe one based on system.text.json, but that's maybe future.

--

I'll think some more on this...

[springcomp]

I would love if we could switch to System.Text.Json.
That’s a ton of work though.

[springcomp]

You can absolutely renamed .Interop to .Abstractions indeed.
That library has never been published as a NuGet and is somewhat of an internal implementation details.