Skip to content

Add trial token support#2201

Merged
crazywoola merged 3 commits intolanggenius:mainfrom
yjcia:ecommerce_helper
Mar 27, 2026
Merged

Add trial token support#2201
crazywoola merged 3 commits intolanggenius:mainfrom
yjcia:ecommerce_helper

Conversation

@yjcia
Copy link
Copy Markdown
Contributor

@yjcia yjcia commented Mar 24, 2026

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

  1. Add trial token support

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

No

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

1. 增加试用token
Copy link
Copy Markdown
Member

@crazywoola crazywoola left a comment

Choose a reason for hiding this comment

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

Thanks for the update. I ran the package through local marketplace checks for PR #2201.

Check Status Required action
Single .difypkg ✅ Pass None
PR language ✅ Pass None
Project structure (manifest.yaml, README.md, PRIVACY.md, _assets/) ✅ Pass None
README language ✅ Pass None
Credential wiring ❌ Fail Add credentials_for_provider entries to provider/ecommerce_helper.yaml and read those configured values at runtime instead of hardcoding TOKEN = "test_token" in the tool implementations
Monthly sales token handling ❌ Fail Remove the trailing comma in token = TOKEN, so the request sends a string token rather than a tuple
dify_plugin version ❌ Fail Bump the lower bound from >=0.4.0 to >=0.5.0 in requirements.txt
Install test ✅ Pass None
Packaging test ✅ Pass None

Next steps

  • Define provider credentials for the required tokens in provider/ecommerce_helper.yaml.
  • Replace the hardcoded test_token usage in both tools with the configured runtime credentials.
  • Fix token = TOKEN, in the monthly sales tool.
  • Update dify_plugin to >=0.5.0.

After those changes, this should be ready for another pass.

yjcia added 2 commits March 25, 2026 15:17
1. Define provider credentials for the required tokens in provider/ecommerce_helper.yaml.
2. Replace the hardcoded test_token usage in both tools with the configured runtime credentials.
3. Fix token = TOKEN, in the monthly sales tool.
4. Update dify_plugin to >=0.5.0.
@yjcia
Copy link
Copy Markdown
Contributor Author

yjcia commented Mar 25, 2026

Hi @crazywoola

Thanks for your review. I have fixed above issues.
Please kindly review again.

Thanks.

@crazywoola crazywoola merged commit 712003f into langgenius:main Mar 27, 2026
1 check 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.

2 participants