A Go (golang) implementation of dotenv.
alexsasharegan/browser-http-client 3
Browser-focused, type-safe, lightweight XHR client.
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
PHP password hashing utilities
alexsasharegan/alexsasharegan.github.io 0
Master page for all my open source projects.
Parser for apache logs.
A curated list of awesome things related to Vue.js
issue openedalexsasharegan/vue-functional-data-merge
created time in 9 days
issue commentalexsasharegan/vue-functional-data-merge
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.
comment created time in 9 days
issue commentalexsasharegan/vue-functional-data-merge
Okay, yup. Vue.version is a thing. Not seeing it documented, but it's on the global.
comment created time in 12 days
issue commentalexsasharegan/vue-functional-data-merge
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.
comment created time in 12 days