You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some special cases, the generic rules used by the migration tooling might not be suitable and a developer might decide to revert a migration step done by the tooling.
In that case, it would be helpful for a repeated usage of the tooling, if the corresponding code location could be marked as 'don't touch'. It might however be tricky to express what shouldn'T be touched
what exact part of the code shouldn't be touched (e.g. only part of a line or a range starting somewhere in one line and continuing to some other line)
what change should not be applied? How to prevent that new migration rules are also blocked by old comments
The text was updated successfully, but these errors were encountered:
In some special cases, the generic rules used by the migration tooling might not be suitable and a developer might decide to revert a migration step done by the tooling.
In that case, it would be helpful for a repeated usage of the tooling, if the corresponding code location could be marked as 'don't touch'. It might however be tricky to express what shouldn'T be touched
The text was updated successfully, but these errors were encountered: