Skip to content

Modified the scripts to allow unfiltered SDK for testing#552

Merged
mchatlas-hellosign merged 1 commit into
mainfrom
allow-building-unflitered-sdk-for-testing
Jun 15, 2026
Merged

Modified the scripts to allow unfiltered SDK for testing#552
mchatlas-hellosign merged 1 commit into
mainfrom
allow-building-unflitered-sdk-for-testing

Conversation

@mchatlas-hellosign

Copy link
Copy Markdown
Member

This allows creating a second, unfiltered yaml that can be used to create an SDK containing all normally hidden fields for internal testing

@mwojcik-dropbox mwojcik-dropbox left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it looks good. If I understand correctly running build with --testing flag will generate additional OA file which will be then used to generate sdk which will be zipped for the test SDK for new features testing?

@mchatlas-hellosign

Copy link
Copy Markdown
Member Author

yes, that's the idea. This way the unfiltered input is never saved to the "main" files so we don't risk pushing it to docs or public SDKs

@mchatlas-hellosign mchatlas-hellosign merged commit ff5ed29 into main Jun 15, 2026
9 checks passed
@mchatlas-hellosign mchatlas-hellosign deleted the allow-building-unflitered-sdk-for-testing branch June 15, 2026 14:18
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