Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
None
Purpose of change
Closes #73967
Migration good
Describe the solution
Adds basic JSON field type migration
Adds a test to check it works
Adds it to the docs
Removes reading ancient legacy ints that corresponded to field types, if it tries to read a legacy int it silently skips that field types members and then continues normally.
Doesn't remove the legacy functions etc, will clean up in a separate PR.
Describe alternatives you've considered
Not letting Erk get away with renaming ids just because they don't like them
Nesting the ter/furn and field migration checks inside their respective non migration checks
Testing
Compiles and loads, tests compile, existing field submap test and new migration one both pass
Additional context