Skip to content
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

refactor(spec): add uint8 for int encoding and templatize #711

Merged
merged 8 commits into from
Aug 28, 2024

Conversation

archerzz
Copy link
Member

  • .net doesn't support uint32 yet, so use uint8
  • use a value which will be negative in signed int

Cadl Ranch Contribution Checklist:

  • I have written a scenario spec
  • I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
  • I have written a mock API
  • I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

- .net doesn't support uint32 yet, so use uint8
- use a value which will be negative in signed int
Copy link

changeset-bot bot commented Aug 23, 2024

🦋 Changeset detected

Latest commit: 43c7331

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@azure-tools/cadl-ranch-specs Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@archerzz archerzz changed the title refactor(spec): replace uint32 with uint8 for int encoding refactor(spec): add uint8 for int encoding and templatize Aug 27, 2024
@archerzz archerzz merged commit cca6fdf into Azure:main Aug 28, 2024
9 checks passed
@archerzz archerzz deleted the improve-int-encode branch August 28, 2024 03:18
v-hongli1 pushed a commit to v-hongli1/cadl-ranch that referenced this pull request Aug 29, 2024
- .net generator doesn't support `uint32` yet, so add a `uint8` test case
- templatize int encoding test cases

---------

Co-authored-by: Mingzhe Huang (from Dev Box) <[email protected]>
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.

3 participants