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.

Sign up for GitHub

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

Jump to bottom

feature: Evolve an API by Renaming a Field #2490

Open
1 task
stevekuznetsov opened this issue Dec 14, 2022 · 0 comments
Open
1 task

feature: Evolve an API by Renaming a Field #2490

stevekuznetsov opened this issue Dec 14, 2022 · 0 comments
Labels
area/apiexports kind/feature Categorizes issue or PR as related to a new feature.

Comments

@stevekuznetsov
Copy link
Contributor

Feature Description

As a service provider exposing an API through an export,
I would like to rename an existing field in my API while retaining user data
In order to better document the features I support

Proposed Solution

We need to make sure that:

  • the API author owns the storage version
  • regardless of the storage version and client's requested version, the data stays in sync and is appropriately exposed to the client

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response
@stevekuznetsov stevekuznetsov added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 14, 2022
@stevekuznetsov stevekuznetsov moved this to New in kcp Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/apiexports kind/feature Categorizes issue or PR as related to a new feature.
Projects
kcp
Status: New
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ncdc @stevekuznetsov