-
Notifications
You must be signed in to change notification settings - Fork 17
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
fix(generator): handle custom request escaping #313
Conversation
✅ Deploy Preview for api-clients-automation canceled.
|
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
ffcf747
to
910b62e
Compare
910b62e
to
6008884
Compare
6008884
to
b81a580
Compare
b81a580
to
a1396b9
Compare
#318 should fix the generation for the PHP client |
87e0614
to
5cebd4a
Compare
5cebd4a
to
5a79f54
Compare
I think the title should be |
@@ -382,7 +384,7 @@ runs: | |||
if: ${{ inputs.job == 'cts' || inputs.job == 'codegen' }} | |||
uses: actions/cache@v2 | |||
with: | |||
path: clients/algoliasearch-client-php | |||
path: clients/algoliasearch-client-php/lib/Api/RecommendApi.php |
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.
I don't think this will work once we remove the generated code, this is not the only generated file, there are other as listed here,
the easiest is to keep clients/algoliasearch-client-php
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.
I don't think this will work once we remove the generated code
This should be tackled once we encounter the issue
the easiest is to keep clients/algoliasearch-client-php
The cache contains the whole folder, not only the changes, so the latest restoration will override all the previous ones
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.
I don't think we should break something to fix it later, is it an issue right now ?
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.
The cache is restored only if nothing has changed in theory, I don't see the issue
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.
I don't think we should break something to fix it later, is it an issue right now ?
It does not seem to work right now
This is the commit for the same generated code for same cache path: 1c27d48
32e25c8
to
558cbf0
Compare
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.
Let's go !
algolia/api-clients-automation#313 Co-authored-by: Clément Vannicatte <[email protected]>
algolia/api-clients-automation#313 Co-authored-by: Clément Vannicatte <[email protected]>
algolia/api-clients-automation#313 Co-authored-by: Clément Vannicatte <[email protected]>
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-350
Changes included:
Follow up of #315
x-is-custom-request
variable to the templates to avoid encoding path parameters of custom requestsesm
from bundlesize🧪 Test
CI :D