Skip to content

Commit 9dd7da2

Browse files
authored
Fix broken YAML example code in README (#1352)
1 parent 03826e3 commit 9dd7da2

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

README.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -506,6 +506,7 @@ In this case we override the package with its local copy, which should have a `s
506506

507507
```yaml
508508
workspace:
509+
packageSet:
509510
registry: 41.2.0
510511
extraPackages:
511512
aff:
@@ -538,6 +539,7 @@ In this case, we can just change the override to point to some commit of our for
538539

539540
```yaml
540541
workspace:
542+
packageSet:
541543
registry: 41.2.0
542544
extraPackages:
543545
aff:
@@ -560,7 +562,8 @@ There are a few possible scenarios - the most straightforward is when a package
560562

561563
```
562564
workspace:
563-
registry: 41.2.0
565+
packageSet:
566+
registry: 41.2.0
564567
extraPackages:
565568
some-package-from-the-registry: 4.0.0
566569
```
@@ -569,6 +572,7 @@ Another possibility is that the package is not in the registry (maybe it's your
569572

570573
```yaml
571574
workspace:
575+
packageSet:
572576
registry: 41.2.0
573577
extraPackages:
574578
facebook:
@@ -584,6 +588,7 @@ The last possible case is the one picking up a local folder as a package (note:
584588

585589
```yaml
586590
workspace:
591+
packageSet:
587592
registry: 41.2.0
588593
extraPackages:
589594
facebook:

0 commit comments

Comments
 (0)