profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jvissers/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

jvissers/profiletest 1

Shows how Spring Profiles work

jvissers/eclipselink 0

Eclipselink project

jvissers/htmx 0

</> htmx - high power tools for HTML

jvissers/itwercks 0

Bootstrapping github/wercker

jvissers/jaxb2-maven-plugin 0

JAXB2 Maven Plugin

jvissers/micronaut-data 0

Ahead of Time Data Repositories

jvissers/TypeScript-Website 0

The Website and web infrastructure for learning TypeScript

jvissers/utf8.java 0

Vectorized UTF-8 Validation for Java

jvissers/wiremock 0

A tool for mocking HTTP services

PR opened ueberdosis/tiptap

Use pasteRegex in addPasteRules

Seems like inputRegex was used in addPasteRules by mistake (?)

+1 -1

0 comment

1 changed file

pr created time in 5 days

push eventjvissers/tiptap

Jan Vissers

commit sha ec4c7f319214c38d744d6e9e71f29e2069dac9fc

Use pasteRegex in addPasteRules Seems like inputRegex was used in addPasteRules by mistake (?)

view details

push time in 5 days

fork jvissers/tiptap

The headless editor framework for web artisans.

https://tiptap.dev

fork in 5 days

issue openedueberdosis/tiptap

VueNodeView compose misses 'expose' in call to SCI setup block

Description The following should be equivalent but are not.

`<script> import { NodeViewWrapper, NodeViewContent, nodeViewProps } from '@tiptap/vue-3'

export default { components: { NodeViewWrapper, NodeViewContent, },

props: nodeViewProps, } </script>`

versus

<script lang="ts" setup> import { NodeViewContent, nodeViewProps, NodeViewWrapper } from '@tiptap/vue-3'

defineProps(nodeViewProps) </script>

The second variation gives an undefined in the call from VueNodeView to setup for expose

created time in 6 days

PR opened bigskysoftware/htmx

Make explicit that AlpineJS should register events in Kebab case

AlpineJS needs Kebab case registrations of HTMX events to work properly.

+3 -1

0 comment

1 changed file

pr created time in 22 days

push eventjvissers/htmx

Jan Vissers

commit sha 5cf9c44f84eecb95bc52e534c80b511b4d859407

Make explicit that AlpineJS should register events in Kebab case AlpineJS needs Kebab case registrations of HTMX events to work properly.

view details

push time in 22 days

push eventjvissers/htmx

Jan Vissers

commit sha 85107c9ac12dfa9c623f998c3a8fac2e7a943be3

Events need to be specified in Kebab case for AlpineJS Made explicit that AlpineJS requires events to be registered in Kebab case.

view details

push time in 23 days

fork jvissers/htmx

</> htmx - high power tools for HTML

https://htmx.org

fork in 23 days

push eventjvissers/TypeScript-Website

Jan Vissers

commit sha 7643622726f6ece8ec83876ee359a877888ad797

firstElement examples should take into consideration undefined - revised The behavior of the return type of 'firstElement' will differ based on the setting of https://www.typescriptlang.org/tsconfig#noUncheckedIndexedAccess. When this is set to 'true' the original example will not compile. By being more explicit in the return type (i.e. using: T | undefined) the code compiles regardless of that setting and beyond that expresses intent (even) more clearly.

view details

push time in a month

pull request commentmicrosoft/TypeScript-Website

firstElement examples should take into consideration undefined

Wow - that was quick :)

Your call, again I'm really new at this. For what it is worth, I think (then) the most explicit way to write this would be to have T | undefined

jvissers

comment created time in a month

PR opened microsoft/TypeScript-Website

firstElement examples should take into consideration undefined

function firstElement<T>(arr: T[]): T

Started experimenting (n00b alert) with TS (4.3.5) and the above example does not compile. It gives me:

Type 'T | undefined' is not assignable to type 'T'.
  'T' could be instantiated with an arbitrary type which could be unrelated to 'T | undefined'. ts(2322)

There are two alternatives I think:

  1. leave the function result T and let TS inference deal with it
  2. specified T | undefined as function result
+5 -3

0 comment

1 changed file

pr created time in a month

push eventjvissers/TypeScript-Website

Jan Vissers

commit sha 0e2df869a68846bfba78505c39f4de9f31b808f3

firstElement examples should take into consideration undefined function firstElement<T>(arr: T[]): T Started experimenting (n00b alert) with TS (4.3.5) and the above example does not compile. It gives me: Type 'T | undefined' is not assignable to type 'T'. 'T' could be instantiated with an arbitrary type which could be unrelated to 'T | undefined'. ts(2322) There are two alternatives I think: 1. leave the function result T and let TS inference deal with it 2. specified T | undefined as function result

view details

push time in a month

fork jvissers/TypeScript-Website

The Website and web infrastructure for learning TypeScript

https://www.typescriptlang.org

fork in a month

startedueberdosis/tiptap

started time in a month