Closed davidlehn closed 4 years ago
Perhaps we should add tests that would flesh out the need for this.
Intuitively, if pushing onto a shared stack when processing a named graph, you would need to revert to the previous state after processing, but a test that could fail would be useful. Or, if we can't come up with one, perhaps it's not really necessary after all.
See https://github.com/w3c/json-ld-framing/pull/97, I now believe graphStack
serves no purpose.
lib/frame.js
tracks graphs withstate.graphStack
but it doesn't look like they are used.@gkellogg Was there a plan for this? Pending tests that would need it? Maybe something that didn't make it over from ruby?
It might be a good point for a debugging hook.