Skip to content

Fix property and event names for popconfirm component - #20240

Merged
iamkun merged 2 commits into
ElemeFE:devfrom
hugiron:fix/popconfirm-event-names
Oct 29, 2020
Merged

Fix property and event names for popconfirm component#20240
iamkun merged 2 commits into
ElemeFE:devfrom
hugiron:fix/popconfirm-event-names

Conversation

@hugiron

@hugiron hugiron commented Sep 26, 2020

Copy link
Copy Markdown
Contributor

Please make sure these boxes are checked before submitting your PR, thank you!
https://vuejs.org/v2/guide/components-custom-events.html

Vue.prototype.$emit = function (event) {
    // before
    var lowerCaseEvent = event.toLowerCase();
    // after
}

@element-bot

element-bot commented Sep 26, 2020

Copy link
Copy Markdown
Member

Deploy preview for element ready!

Built with commit 9c43018

https://deploy-preview-20240--element.netlify.app

@hugiron

hugiron commented Sep 26, 2020

Copy link
Copy Markdown
Contributor Author

@iamkun take a look
This fix is urgently needed

@ja-peng

ja-peng commented Nov 5, 2020

Copy link
Copy Markdown

long time no see

@wulucxy

wulucxy commented Nov 5, 2020

Copy link
Copy Markdown

这种mr 也能合并,线上全部确认事件无效了
???

@xx45

xx45 commented Nov 5, 2020

Copy link
Copy Markdown

@wulucxy element 更新日志里都写了是不兼容升级 , 自己不看就乱升级线上环境 真是头铁

@wulucxy

wulucxy commented Nov 5, 2020

Copy link
Copy Markdown

@xx45 去了解下 npm 版本规则,minor 版本是自动升级的。这种breaking change 放在 minor 版本要害死一堆程序员了

@xx45

xx45 commented Nov 5, 2020

Copy link
Copy Markdown

生产环境锁版本 这不是基本操作

@wulucxy

wulucxy commented Nov 5, 2020

Copy link
Copy Markdown

@xx45 建议多参考业界的实践
https://zhuanlan.zhihu.com/p/22934066

@climba03003

climba03003 commented Nov 5, 2020

Copy link
Copy Markdown

版本控制也不是全部人都跟隨 semver
例如很多人用的TypeSciprt X.Y.Z 當中 ``X.Y``` 都是主要版本

怕出事就最好用 ~X.Y.Z / X.Y.x 來做依賴版本管控
這樣不影響功能又可以更新Patch

當然最穩定做法是人手更新

@raydao

raydao commented Nov 10, 2020

Copy link
Copy Markdown

这次也没有太多的更新,线上项目没有更新了

@Jibacat

Jibacat commented Nov 18, 2020

Copy link
Copy Markdown

建议下次版本升级的时候进行兼容性处理,先同时保留confirm/cancel和onConfirm/onCancel两组事件,然后在3.x版本再将onConfirm/onCancel废弃

@furylee

furylee commented Nov 27, 2020

Copy link
Copy Markdown

建议下次版本升级的时候进行兼容性处理,先同时保留confirm/cancel和onConfirm/onCancel两组事件,然后在3.x版本再将onConfirm/onCancel废弃

果然,除了客户端

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants