John Patrick Morgan

Thanks for raising this issue. I completely agree, they should be preserved. They are currently parsed but not used as part of the UI. I'll mark this as an enhancement,...

Thanks for this suggestion. I agree it would be great to combine the constraints into a single diagram, and it’s something I’d been hoping to add. It might be difficult...

Thanks a lot for raising this issue. Being able to edit view names would be a nice enhancement, and might fit well with #7. It might also be useful to...

Thanks for raising this issue. You're right that the parser doesn't currently handle the output of constraints made that way, but I believe that support can be added.

Thanks for raising this issue. This relates to the `identifier` parser in `ConstraintsParser+Instances.swift`: https://github.com/johnpatrickmorgan/wtfautolayout/blob/823cdf9bd10cd416d313b6b131e16cc0995abafa/Sources/App/Parsing/ConstraintsParser%2BInstances.swift#L36 Currently it does not allow single-quote marks, which stops it from greedily consuming the whole line...

Thanks, yes that seems like a good short-term approach. As an aside, I think _U+2019_ is the preferred character for possessive apostrophes, which would avoid the issue in this case...

Thank you very much for documenting these errors. I believe the first two are due to the lack of support for constraints using NSLayoutDimensions based on multiple anchors (similar to...

Thanks for raising this issue. I was under the impression that constraints that have been translated from autoresizing masks have an additional piece of info in their description, in the...

@pipelineoptika Thanks very much for the additional info; I will have a deeper look. Just to check, are you using any Auto Layout frameworks such as SnapKit in that project?

Thanks for raising an issue. Just to check I understand properly: It would be useful to add a checkbox for each constraint, so that a user can mark each constraint...