strmnn Posts

strmnn

•Created by strmnn on 8/22/2024 in #help

jsdoc `@import` ignored by `deno check` but not by LSP

This code displays an error correctly in VSCode:

/**
 * @import { And } from "@pumpn/type-party";
 */

/**
 * @type {([
 * And<true, true>,
 * And<true, false>,
 * And<false, true>,
 * And<false, false>
 * ])}
 */
const result = [
    true,
    false,
    false,
    true // Type 'true' is not assignable to type 'false'.deno-ts(2322)
];

export default result;

/**
 * @import { And } from "@pumpn/type-party";
 */

/**
 * @type {([
 * And<true, true>,
 * And<true, false>,
 * And<false, true>,
 * And<false, false>
 * ])}
 */
const result = [
    true,
    false,
    false,
    true // Type 'true' is not assignable to type 'false'.deno-ts(2322)
];

export default result;

But running deno check on the same file emits no error at all. If one now changes the code to use the more verbose @typedef way of importing jsdoc types:

/**
 * @template {boolean} A
 * @template {boolean} B
 * @typedef {import("@pumpn/type-party").And<A,B>} And<A,B>
 */

/**
 * @type {([
 * And<true, true>,
 * And<true, false>,
 * And<false, true>,
 * And<false, false>
 * ])}
 */
const result = [
    true,
    false,
    false,
    true // Type 'true' is not assignable to type 'false'.deno-ts(2322)
];

export default result;

/**
 * @template {boolean} A
 * @template {boolean} B
 * @typedef {import("@pumpn/type-party").And<A,B>} And<A,B>
 */

/**
 * @type {([
 * And<true, true>,
 * And<true, false>,
 * And<false, true>,
 * And<false, false>
 * ])}
 */
const result = [
    true,
    false,
    false,
    true // Type 'true' is not assignable to type 'false'.deno-ts(2322)
];

export default result;

The errors appear in both VSCode and deno check. What am I doing wrong?

1 replies

DDeno

•Created by strmnn on 11/20/2022 in #help

Deno Deploy and Digital Ocean PostgreSQL DB...how on earth?

https://github.com/denoland/deno/issues/10312 So since the issue above seems to take quite some time to fix because it apparently involves several upstream software, is there anyway to fix the "other side"? What specifically is so special about (for example) Digital Ocean's ca certificates that they are completely unusable with Deno/Deno Deploy/rustls/webpki (whatever the latter two are). I assume this isn't the case with every other certificate issuer or service or host (sorry I don't understand a lot about this, it's all a bit complex). I assume people are successfully connecting to their databases on other services through Deno. What I mean, is there any point in asking Digital Ocean support if they can workaround this on their side? Are they even able to do that? Is there anything I can do locally? Does anybody know of an alternative route/service that works? Sorry this sounds so desperate, but I have this specific issue for months now on a big project I finally want to release, feel like I have apparently chosen the two most incompatible services (DO & Deno Deploy) and wish I would at least know from which service I have to migrate my whole project away from (again...). More specifically, does anybody have a working example of - connecting to a PostgreSQL managed database on Digital Ocean from a server running on Deno Deploy - or connecting to a PostgreSQL managed database on Digital Ocean from any other Deno hosting service - or connecting to a PostgreSQL managed database on any other service from a server running on Deno Deploy?

9 replies