-
Notifications
You must be signed in to change notification settings - Fork 277
[http-specs] Add test cases for additional special words #7431
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
base: main
Are you sure you want to change the base?
Conversation
@copilot Could you fix the build issue? |
@opNameScenario("get") get(): void; | ||
@opNameScenario("implements") `implements`(): void; | ||
@opNameScenario("instanceof") `instanceof`(): void; | ||
@opNameScenario("interface") `interface`(): void; |
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.
Fix the ci failure for pnpm validate-scenarios
.
Co-authored-by: MaryGao <[email protected]>
I've fixed the build issue by properly marking 'declare' as a reserved keyword. TypeSpec requires reserved keywords to be wrapped in backticks. I've updated all instances of 'declare' in the code (operations, parameters, model names, and model references). The validation now passes successfully. (d6983ab) Warning Firewall rules blocked me from connecting to one or more addressesI tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
This PR adds test cases for a comprehensive set of additional special words to the http-specs package. These special words are important to test since they could potentially cause issues in code generation across different language targets.
The changes include:
any
,boolean
,case
,catch
,const
, etc.main.tsp
mockapi.ts
These additions will help ensure that generators handling TypeSpec code properly escape reserved words in their target languages, especially for the TypeScript generators as referenced in Azure/autorest.typescript#3192.
The complete list of added special words:
Fixes #7420.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
cdn.fwupd.org
/usr/bin/fwupdmgr refresh
(dns block)crl3.digicert.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js
(dns block)crl4.digicert.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)ocsp.digicert.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js
(dns block)s.symcb.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)s.symcd.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)ts-crl.ws.symantec.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)ts-ocsp.ws.symantec.com
dotnet build --configuration Release -p:Version=1.0.0 -clp:NoSummary
(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.