profile
viewpoint
Alex Regan alexsasharegan Parametric Studios Phoenix, AZ http://parametricstudios.com/ Love code and puppies 🐶🐶

alexsasharegan/dotenv 17

A Go (golang) implementation of dotenv.

alexsasharegan/browser-http-client 3

Browser-focused, type-safe, lightweight XHR client.

alexsasharegan/Database_lib 2

A dependency free, light PHP mysqli library to properly handle errors, connections, and make getting data simple and DRY.

alexsasharegan/atom-snippets 1

My atom snippets

alexsasharegan/crypto_lib 1

PHP password hashing utilities

alexsasharegan/alexsasharegan.github.io 0

Master page for all my open source projects.

alexsasharegan/apache-log 0

Parser for apache logs.

alexsasharegan/awesome-vue 0

A curated list of awesome things related to Vue.js

issue commentalexsasharegan/vue-functional-data-merge

Vue 3 support

Looks like the safest way to do this is a new version like you suggested. I thought it might be nice for the library to detect and use the right merge strategy, but that creates a big question of accessing the Vue global to determine version, and that often leads to build hassles and sometimes double packaging all of Vue.

jackmu95

comment created time in 9 days

issue commentalexsasharegan/vue-functional-data-merge

Vue 3 support

Okay, yup. Vue.version is a thing. Not seeing it documented, but it's on the global.

jackmu95

comment created time in 12 days

issue commentalexsasharegan/vue-functional-data-merge

Vue 3 support

I will check out how things should change to accommodate the new props interface! I won't get to it right away, so perhaps you can point me to where I could do a vue version check to switch the merge function accordingly? Hopefully there's something simple like Vue.version I can check.

jackmu95

comment created time in 12 days

more