-
Notifications
You must be signed in to change notification settings - Fork 3
docs: add license configuration examples for SDK generators #1755
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
Conversation
- Add license field example to metadata section in generators-yml-reference.mdx - Add ParamField documentation for license configuration - Add license example to Python publishing guide Co-Authored-By: danny@buildwithfern.com <danny@buildwithfern.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
| </ParamField> | ||
|
|
||
| <ParamField path="license" type="'MIT' | 'Apache-2.0'" required={false} toc={true}> | ||
| Software license for the generated SDK. Supported values are `MIT` or `Apache-2.0`. This populates the license field in package manifests (e.g., `pyproject.toml` for Python, `package.json` for TypeScript). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[FernStyles.Acronyms] 'MIT' has no definition.
|
@devalog added per this slack thread |
@dannysheridan |
docs: add license configuration examples for SDK generators
Summary
Adds documentation for how to specify a license for generated SDKs using the
metadata.licensefield. This addresses customer confusion about where to configure licenses ingenerators.yml.Changes:
license: MITexample to the top-level metadata section ingenerators-yml-reference.mdxmetadata.licenseacceptsMITorApache-2.0and populates package manifestslicense: MITexample to the Python publishing guide showing the correct placement at the generator levelReview & Testing Checklist for Human
metadata.license: MITand confirm it populates thelicensefield inpyproject.tomland adds the appropriate PyPI classifieroutput.metadata(PyPI-specific) andmetadata(general SDK metadata). Confirm this isn't confusing for usersNotes
This was a minimal change per Danny's request to "change less rather than more." The customer originally tried using
pyproject_tomlunderconfigwhich doesn't work - the correct location ismetadata.licenseat the generator level.Link to Devin run: https://app.devin.ai/sessions/62df5dfa1f934ae5b60671d82da03897
Requested by: danny@buildwithfern.com (@dannysheridan)