Tomasz Pluskiewicz

I have recently updated this plugin in a TS project and I find this rule conflicted with latest typescript. I inherit from LitElement, so the `connectedCallback` is definitely there. If...

Sure, that would also be [less surprising](https://en.wikipedia.org/wiki/Principle_of_least_astonishment) and indeed Polymer elements do come to mind as an example of established practices. On the other hand some `paper`/`iron` packages actually come...

That would work I guess. It's up to you if you would be content with mixed output like of object lists such as ```turtle ex:prop "foo" , "bar" , "baz"...

In case you're interested, I implemented a transform stream which consumes an RDF/JS stream first building up a `c4(r)` structure and passing that to graphy: [TransformToConciseHash](https://github.com/zazuko/rdfjs-elements/blob/master/packages/formats/serializers/TransformToConciseHash.js) It takes care to...

And Trig :)

Yes, makes total sense. The thing is that in this particular repo I'm not in fact using Netlify for deployment but I found your action so that I can have...

Maybe. The PR check could be created using a separate action. Probably does not belong here anyway. I was only thinking to maybe output the deployed URL. Do you know...

Following an arduous trial and error process, I landed [this workflow](https://github.com/hypermedia-app/shaperone/blob/master/.github/workflows/netlify.yml) which combines your action with a status check. I will create a PR with example usage. An action input...

FWIW, I think fig should keep suggesting both `remotes/{remote}/{branch}` as well as `{branch}` but prioritising the latter

ping