Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE #4658] Add documentation for dingtalk sink connector. #4660

Merged
merged 2 commits into from
Dec 16, 2023

Conversation

yanrongzhen
Copy link
Contributor

@yanrongzhen yanrongzhen commented Dec 16, 2023

Fix #4658

Modifications

Add documentation for dingtalk sink connector.

Comment on lines +2 to +4

## DingtalkSinkConnector:from eventmesh to dingtalk。

Copy link
Member

@Pil0tXia Pil0tXia Dec 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will be better to remove this CN period and use EventMesh and DingTalk instead. Or I will do it later.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in #4668.

@xwm1992 xwm1992 added this to the 1.10 milestone Dec 16, 2023
Copy link

codecov bot commented Dec 16, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f17b82e) 17.39% compared to head (c859c8c) 17.39%.

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #4660   +/-   ##
=========================================
  Coverage     17.39%   17.39%           
- Complexity     1758     1759    +1     
=========================================
  Files           797      797           
  Lines         29787    29787           
  Branches       2575     2575           
=========================================
+ Hits           5180     5182    +2     
+ Misses        24129    24128    -1     
+ Partials        478      477    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

```yaml
pubSubConfig:
# default port is 10000
meshAddress: 127.0.0.1:10000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you change it to your.eventmesh.server:10000 like this document? This may be clearer.

能否像该文档一样改成这样your.eventmesh.server:10000 ?这样也许更明确。

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in #4668.

@@ -0,0 +1,26 @@
# eventmesh-connector-dingtalk
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This connector has requirements for data properties, but it seems that your document does not specify them. #4591 (comment)

该Connector对数据的属性是有要求的,您的文档好像没有说明。#4591 (comment)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in #4668.

@mxsm mxsm merged commit 61e1392 into apache:master Dec 16, 2023
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Doc] Documentation Needed for eventmesh-connector-dingtalk
5 participants