灵活易用的nodejs后端框架
AngularJS directives for Semantic-UI
ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.
a lightweight、high-performance and easy-to-follow javascript MVVM framework
基于avalon的组件库
dsonet/bilibili-backup-backup 0
你还要我怎么样嘛 备份的备份（
Standard Library
🥚 Born to build better enterprise frameworks and apps with Node.js & Koa
A core Pluggable framework based on koa.
dsonet/elasticsearch-analysis-hanlp 0
HanLP Analyzer for Elasticsearch
Pull request review commentvuejs/vue-next
feat(renderList): warn with `v-for` has non-integer range number
export function ssrRenderList( } } else if (typeof source === 'number') { if (__DEV__ && !Number.isInteger(source)) {- warn('Please give an non-integer value for v-for range.')+ warn('Please give an integer value for v-for range.')
Better to include the source so that easier to find out the cause.
comment created time in 19 hours
Pull request review commentvuejs/vue-next
feat(renderList): warn with `v-for` has non-integer range number
export function ssrRenderList( } } else if (typeof source === 'number') { if (__DEV__ && !Number.isInteger(source)) {- warn('Please give an non-integer value for v-for range.')+ warn('Please give an integer value for v-for range.')
v-for range expect an integer value but got ${source}.
comment created time in 19 hours
startedvuejs/vue-next
started time in 2 days
pull request commentvuejs/vue-next
fix(reactivity): use `resetTracking` instead of `enableTracking` in baseHandlers.ts
Why?
comment created time in 3 days
pull request commentzenoamaro/react-quill
I think code formatting should be in a separate PR.
comment created time in 6 days
pull request commentarangodb/arangojs
doc: Update to correct constructor config prop
Thank you very much. I was wonder what's wrong with my code since I follow the examples. Turns out the example was wrong:(
comment created time in 7 days
pull request commentvuejs/vue-next
Remove useless else statements
This decreased the code readability A LOT.
comment created time in 7 days
issue commentvuejs/vue-next
Array.prototype.push/pop/shift/unshift cause infinite recursion
What about method splice?
comment created time in 11 days
pull request commentvuejs/vue-next
fix(reactivity): Array.prototype.push causes infinite recursion
@unbyte If so, unshift should also be included.
comment created time in 12 days
pull request commentvuejs/vue-next
fix(computed): add computedRunners
I think it actually doesn't matter. Because in the end the value was correct.
comment created time in 14 days
startedTencent/omi
started time in 19 days
Pull request review commentvuejs/vue-next
fix(runtime-dom): v-model breaks minlength validation
function baseCreateRenderer( const prev = oldProps[key] const next = newProps[key] if (- next !== prev ||- (hostForcePatchProp && hostForcePatchProp(el, key))+ (hostForcePatchProp && hostForcePatchProp(el, key)) ||+ next !== prev
Why do you change this order? Typically a compare operation would be lighter than a method invoke. It's reasonable to have the comparison ahead.
comment created time in a month
pull request commentvuejs/vue-next
fix(runtime-dom): v-model breaks minlength validation
Why not just compare the 2 values? The less involved the better performance.
comment created time in a month
pull request commentvuejs/vue-next
fix(runtime-core/scheduler): use undefined instead of null
Talking about the readability, I think the current one is better. It's clearer to have the logic in an if branch, focus on what we should deal with. With an extra return, it does reduce the indent but definitely increase the cost of reading the code, you have to keep reminding yourself it's actually introduced an else branch.
comment created time in a month
startedprocessing/p5.js
started time in 2 months
startedalexandersimoes/d3plus
started time in 2 months
startedunconed/mathbox
started time in 2 months
startedmrdoob/three.js
started time in 2 months
PR opened ecomfe/zrender
pr created time in 2 months
push eventdsonet/zrender
commit sha 1a8dcbbf0043d5a3eb17a71cb985a7b1f0b4f0da
fix window !== 'undefined' branch ends too early
push time in 2 months
fork dsonet/zrender
A lightweight canvas library which providing 2d draw for ECharts
https://ecomfe.github.io/zrender-doc/public/
fork in 2 months
startedjabez128/jabez128.github.io
started time in 2 months
startedraxxarr/note
started time in 2 months
pull request commentvuejs/rfcs
I think finally can implement the componet import sugar syntax?
<template>
<import src="./Foo.vue" />
<Foo />
</template>
comment created time in 2 months
issue commentvuejs/jsx
I do like this short style, very clean and can be well self explained with hint. <a vOn={[doThat,'click', ['stop','prevent'icsoftfont>} />
It's really unnecessary to introduce extra import just for this syntax hint.
comment created time in 3 months
issue openedOfficeDev/office-js-docs-pr
Comments API doesn't work on Excel version 2006
I tried this API on Excel, but got "This operation is not implemented." I use the latest beta API.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 992f7232-6aa0-b170-ff3b-009a273e7586
- Version Independent ID: 0fd9c00f-91d6-5036-48c9-e0e2e0690e78
- Content: Work with comments using the Excel JavaScript API - Office Add-ins
- Content Source: docs/excel/excel-add-ins-comments.md
- Product: excel
- Technology: add-ins
- GitHub Login: @o365devx
- Microsoft Alias: o365devx
created time in 3 months
startedmidwayjs/midway
started time in 3 months
pull request commentvuejs/vue-next
feat(compiler-ssr): support dynamic components that resolve to element(fix: #1508)
It's may not a good idea to expose this logic in generated ssrRender function. I think the better way is to handle this in library layer.
comment created time in 3 months
pull request commentvuejs/vue-next
fix(reactivity): observe instance from subclass of Collection (close …
It would introduce unnecessary impact of the runtime performance just for very rare user cases., even though it's technically correct. Just like concept vs real world. IMO the best way to deal with it is to put this into limitations section.
comment created time in 3 months
Pull request review commentvuejs/vue-next
fix(reactivity): observe instance from subclass of Collection (close …
}, "[json]": { "editor.defaultFormatter": "esbenp.prettier-vscode"- }+ },+ "deno.enable": false
It would introduce unnecessary impact of the runtime performance just for very rare user cases., even though it's technically correct. Just like concept vs real world. IMO the best way to deal with it is to put this into limitations section.
comment created time in 3 months
startedtootsuite/mastodon
started time in 3 months
pull request commentarangodb/arangodb
@jsteemann About the name IP4, I think the better name is IPv4, it's much more standardized & widely used.
comment created time in 3 months
push eventdsonet/vue-next
commit sha d584e99b71fffd31ba1bc48d71c2ce5f8b9c5bc7
perf(BaseTransition): avoid unnecessary function call
push time in 3 months
startedrainersu/sumi
started time in 3 months