GenType: support @deriving(accessors)
#6537
Merged
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.
@cristianoc As I mentioned here, this change makes results of the
@deriving(accessors)
ppx are also reflected in genType.This is also important to achieve #6196 later. Because, after all, people want correct typing for the whole JS output.
It's not a difficult change here, but requesting every custom ppx author to add the genType attribute themselves. They cannot accurately determine whether the code uses genType or not (currently genType is pretty dependency-aware)
It makes sense to migrate from #6196 to switch to per-file or per-project genType config. A downward is build speed. Obviously, if genType is enabled on the entire project, it will reduce overall build speed somehow. It needs to be measured IMHO.