[Automated] Merge release/september-2023 into main #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fixed microsoft#2664: Add migrate script for zonedDateTime * Update changelog --------- Co-authored-by: Timothee Guerin <[email protected]>
* Add tests. * Progress. * Add test cases. * Progress. * Refactoring and progress. * Make one of the tests pass! Finally! * Second test passing. * Ensure that if a route is shared, all routes are shared. * Add validation for common parameters to be the same type (header, query, etc.) * Fix logic bug in shared operations calcuations. * Code review feedback. * Add documentation for HTTP `@route` decorator. * Code review feedback. * Progress on shared bodies and/or responses. * Refactoring in progress. * Support multiple request body types. * Implementation for multiple response types. * Eliminate assert import. * Simplify logic.
…r use (microsoft#1809) * Fix: Interface with templated operation causing crash if defined after use * Changelog
* Fix diagnostic showing in wrong location * Changelog
* Fixes microsoft#1706. * Add emitter documentation for handling default values. * Update documentation.
Also point to root of WHATWG doc, not the relative string sub-portion.
…#1798) * Add `@sharedRoute` decorator and decouple it from `@route` * Add decorator definitions for @route and @SharedRoute * Add autoRoute shared route tests * Update generated documentation * Deprecate `shared` option for `@route` parameter * Format source * Add `options` signature for `route` decorator * Ensure @action operations have explicit name when using @SharedRoute * Update Rush change files * Update documentation * Update openapi3 shared route tests to use @SharedRoute * PR feedback * Format --------- Co-authored-by: Mark Cowlishaw <[email protected]>
…placeholder, and fix some bugs (microsoft#1839)
* Remove "duplicate-response" error. * Add openapi3 tests. * Closes microsoft#1167. * Refactoring shared routes logic.
* gRPC: initial commit moving from demo to public repo * Added a README * remove copied changelogs * added fresh changelog.json * Some cleanup, removed synthetic models * WIP testing system * Recorded a test * Fixed bug bypassing effective type calculation. * Made 'simple' even simpler. * Added test for inferring message names from context * Supported output message name inference and refactored unreachable types. * Unleaked discriminated union tags. * Updated some documentation. * Capitalize method names, remove space between method name and input type. * Tweaked proto header * Extracted writing reservations into own function * Taught the expectation system to look for diagnostics. * Check for namespace collisions. * Fixed simple-error test * Re-recorded a simple test. * Renamed grpc -> protobuf, improved handling of many protobuf features * Implement cross-package references * Reworked a bunch of docs issues and diagnostics. * Lazy initialize scalars map * Some doc updates * Removed protoc output * Renamed tests to .tsp * Updated diagnostics and some documentation * Updated entrypoint from typespecMain to tspMain * Updated docs * Lint/spell fixes * Updated enum error messages * Improved namespace handling * Reject anonymous models in messages * Removed TODOs * Fixed test harness on windows * addressbook scenario * Several small updates * Ignored .protoc-out integration folder * Updated a few documentation entries * Import from fs rather than import fs * Increased resilience to failed scalar resolutions. * Support derived scalars by traversing the scalar inheritance links. * Add protobuf as website dependency * Just don't support unions for now * Better handling of intrinsic types * Added a note about onValidate * Added a note about syntax target functions * Move a symbol * Add a readme warning.
* Add test cases. * Add more test cases. * Update versioning logic.
…osoft#1863) * Added some utility types to Protobuf and fixed module loading order. * Added protobuf support and preferred emitters to the playground * Updated vite config, removed a console.log * Tweak sample naming * Appropriately cancel compiler debouncing. * Escape a {... not sure how this didn't trigger before. * Refine some types to satisfy the linter.
…#1871) * Issue error when versioned specs specify a single version with @service. Fixes microsoft#1866 (for real this time!) * Apply suggestions from code review Co-authored-by: Timothee Guerin <[email protected]> * Fix up code suggestions. --------- Co-authored-by: Timothee Guerin <[email protected]>
* Add doc errors for decorators and decorator parameters. * Add decorator documentation rules. * Code review feedback. * Update logic. * Compiler docs fixes. * Doc updates. * Fix protobuf issues. * Code review feedback. * Test that build fails... * Add support for scalars. * I hate EVERYTHING about you, cSpell.... * Code review feedback.
Co-authored-by: Mark Cowlishaw <[email protected]>
…crosoft#2335) This PR fixes microsoft#2316 by adding some extra logic to avoid runtime errors when invalid values are given in the `OAuth2Flow` array passed to `OAuth2Auth`.
Fix the link syntax and target --------- Co-authored-by: Mark Cowlishaw <[email protected]> Co-authored-by: David Wilson <[email protected]>
This PR fixes microsoft#2059 by requiring that a semicolon appear after an augment decorator statement. This is a breaking change but it should be mitigated by the fact that the TypeSpec formatter already adds a semicolon for all augment decorator statements.
It looks like CI is failing due to an issue with Babel.js conflicting with Node 20.6: babel/babel#15927 vitejs/vite#14299 For now, let's try pinning Node 20.x to 20.5 until the issue gets fixed in Babel. Comparable `typespec-azure` repo PR: Azure/typespec-azure#3502 Issue Azure/typespec-azure#3504 tracks the work to un-pin the Node version.
…microsoft#2364) fix Azure/typespec-azure#3365 --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]>
…ft#2366) fix [microsoft#2303](microsoft#2303) We don't know if those bodies are mutually exclusive so `anyOf` is more correct. --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]>
fix [microsoft#2230](microsoft#2230) Emitter used value as a number which is like that in later version of openapi (3.1+) --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]>
fix [microsoft#1991](microsoft#1991) Compiler would get into a infinite recursion when comparing recursive models. ```tsp model A { a: A; } model B { a: B; } model Test<T extends A> {} alias T1 = Test<B>; ``` --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]> Co-authored-by: Brian Terlson <[email protected]>
… next statement/node (microsoft#2381) fix [microsoft#2338](microsoft#2338) Issue was when parsing a list we'd get stuck when there is doc comment as the doc comment would change the tracking position and we wouldn't realize the parsing list is not making progress. --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]>
…2375) fix microsoft#1741 --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]>
…crosoft#2273) fix microsoft#2298 Update yaml parser library from `js-yaml` to `yaml` which allow us to have an ast and resolve where values are coming from. Before <img width="973" alt="image" src="https://github.com/microsoft/typespec/assets/1031227/42149942-f077-4058-808f-e3cda2424649"> Now: <img width="904" alt="image" src="https://github.com/microsoft/typespec/assets/1031227/f6544f42-7523-489e-b1dd-335a53668292"> On top of providing error locations for config errors that the compiler can resolve this also setup the base to provide the ability for an emitter to report na error on its emitter options and show where it is. --------- Co-authored-by: Microsoft Auto Changeset Bot <[email protected]>
…refix (microsoft#2337) This change fixes Azure/typespec-azure#3333 by adding a validation step in the `@typespec/http` library which checks whether any referenced operation lives inside of an interface or namespace with a `@route` prefix defined. This check is intended to help a spec author avoid the case where an operation loses the prefix of its referenced operation because it is used outside of the original container. The issue was originally raised in issue microsoft#1466. --------- Co-authored-by: Timothee Guerin <[email protected]> Co-authored-by: Mark Cowlishaw <[email protected]>
fix microsoft#1347 Add syntax highlighting to doc comments. Include the syntax definition for the tmlanguage as well as the semantic highlighting.  [Try it in the playground](https://cadlplayground.z22.web.core.windows.net/prs/2306/?c=LyoqCiAqIEB0ZW1wbGF0ZSBUIFRob3NlIGFyZSBrbm93biB0YWdzIHNvIHdlIGhpZ2hsaWdodCBsaWtlIGtleXdvcmTFQXBhcmFtIGZvbyBUaGlzIGlzIGHEDsscYmFyIC3LHmJhcgogxn5yZXR1cm5zIMgIc3R1ZmbIHWV4YW1wbGXJOm5vdCBhIGRlZmluZWTkAJ7xAJ1kaWZmZXJlbnRseQogKi8KbW9kZWzEcCB7fQo%3D&e=%40typespec%2Fopenapi3&options=%7B%7D) --------- Co-authored-by: Mark Cowlishaw <[email protected]>
fix Azure/typespec-azure#3504 Node 20.6.1 should have resolved the issue Co-authored-by: David Wilson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge refs/heads/release/september-2023 back into main