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

sync with existing resources #93

Open
earloc opened this issue Feb 6, 2023 · 1 comment
Open

sync with existing resources #93

earloc opened this issue Feb 6, 2023 · 1 comment

Comments

@earloc
Copy link
Owner

earloc commented Feb 6, 2023

As a developer, when I export typealized interfaces, I want to sync keys and values with existing files (instead of overwriting them), to not loose any customizations done in them.

@earloc
Copy link
Owner Author

earloc commented Feb 14, 2023

The most significant "problem" currently is, that I do not have a synch-mechanism in place. Currently, The CLI just generates the resource, fast forwarding, overwriting stuff that maybe already has been translated. As code-first is still in a kind of POC phase, atm, so that´s OK for now. But this is definetley a pain point to avoid in the future at all costs.

Diffing those representations is probably not that hard. But the code-first-approach also implies that devs may just rename a property or method, which then would result in a changed key, with little to no chance of accurately being able to diff those with existing resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant