Skip to content

Revamps the constraints workflow#338

Merged
arcanis merged 5 commits into
masterfrom
mael/constraints-workflow
Aug 5, 2019
Merged

Revamps the constraints workflow#338
arcanis merged 5 commits into
masterfrom
mael/constraints-workflow

Conversation

@arcanis
Copy link
Copy Markdown
Member

@arcanis arcanis commented Aug 5, 2019

This diff rearchitects the way we describe constraints in various ways:

  • The gen_invalid_dependency rule is no more 🎉, Yarn will instead infer the right action based on whether there's an ambiguity or not.

  • The gen_enforced_field can now be autofixed (except when an ambiguity arises, same as with ambiguous dependencies).

  • The field values in gen_enforced_field will be parsed into JSON if possible, or will be kept as string otherwise. It means that 1.0 will transform into "1", but "1.0" will stay "1.0".

  • There's a known issue at the moment which is that objects will be compared against each other based on their JSON representation - which may cause issues if the objects are identical apart from their key ordering. PR welcome if you're affected by this 🙂

  • The yarn constraints check command is renamed yarn constraints, and yarn constraints fix is now yarn constraints --fix (to match the ESLint syntax).

Fixes #68, #122

@arcanis arcanis requested a review from bgotink August 5, 2019 13:28
@arcanis arcanis merged commit 5c1906c into master Aug 5, 2019
@arcanis arcanis deleted the mael/constraints-workflow branch August 5, 2019 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Make gen_enforced_field fixable

1 participant