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

Think about how to inform the user about changes in the mapping #135

Open
DedAnton opened this issue May 20, 2023 · 0 comments
Open

Think about how to inform the user about changes in the mapping #135

DedAnton opened this issue May 20, 2023 · 0 comments

Comments

@DedAnton
Copy link
Owner

Let's say the user updated the version of the library, the new version has some kind of bug due to which the user's old mappings stopped working correctly. But he will not know about it, because he is unlikely to check the code of all old mappings. Therefore, a mechanism is needed that will inform him that some changes have taken place.

I like the idea of storing the mapper code somewhere in the project folders so that it gets into the version control system, then when the user commits, the changes will be noticed. Or you can make the system as in testing with snapshots, so that the user is thrown into a diff with some changes, and he had to confirm them. But I think it's overkill in this case.

@DedAnton DedAnton converted this from a draft issue May 20, 2023
@DedAnton DedAnton moved this from To do to Next release in NextGenMapper Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Next release
Development

No branches or pull requests

1 participant