Asbjørn Ulsberg
Asbjørn Ulsberg
I'm struggling with a related problem right now. Before adding the `@11ty/eleventy-plugin-vite` plugin, Eleventy copies the folders I've configured with `addPassthroughCopy()` as expected, but once I add the Vite plugin,...
@KiwiKilian, yep – that fixed it. 🎉 Thanks! 🙏🏼
Isn't this a sensible default? I would expect the same behaviour for all [primitive types](https://www.w3.org/TR/xmlschema-2/#built-in-primitive-datatypes) that can be deduced from the .NET type system.
I agree; `string` and `bool` don't need `@type`. But as .NET has a richer set of types for numbers than JavaScript, I think differentiating between [`float`](https://www.w3.org/TR/xmlschema-2/#float), [`double`](https://www.w3.org/TR/xmlschema-2/#double), [`decimal`](https://www.w3.org/TR/xmlschema-2/#decimal) and [`integer`](https://www.w3.org/TR/xmlschema-2/#integer)...
How would a custom `JsonLdLiteralConverter` be registered? The neatest would be if one class could be registered per literal type, so you don't end up with one gigantic `CustomJsonLdLiteralConverter`. That's...
When a the type is serialised to a `string`, you have no idea whether you actually can deserialise it. We don't have enough contextual information in the `CanConvert()` method to...
Exactly. You would have to set [`TypeNameHandling`](http://www.newtonsoft.com/json/help/html/T_Newtonsoft_Json_TypeNameHandling.htm) to `Objects`, which pollutes the JSON with a `$type` (IIRC) property alongside every value. If we could adjust that to be `@type`, it...
As discussed in HydraCG/Specifications#138, a `Promise` (i.e. callback) based way to handle responses would be nice, so we don't hard code the response expectation into the request side of the...
> Well, fetch is already promise-based so it's a natural pattern to follow with any deferred processing. I'd even use async/await... With `async/await`, the coupling between the request and response...