feat: update @comapeo/schema to 1.2.0, adding alerts and server

[tomasciccola]

this installs a local version of mapeo-schema with remoteDetectionAlert schema.

should close #806

[EvanHahn]

LGTM once we (1) release a new @mapeo/schema (2) fix the type errors.

Could also be good to add a test that runs a remoteDetectionAlert through the whole system to make sure it works. Maybe just create one and make sure we can read it.

[tomasciccola]

I'm getting a type error on the test-e2e/project-crud.js, where I added a fixture for remoteDetectionAlert. I don't know why it expects its field metadata to have a manualLocation. Its basically confusing it with an observation. I can add that field to please the type checker since metadata in remoteDetectionAlert allows for any value for any string key, but it feels finicky.

On the other hand, I can't npm i now, because mapeo/schema is a peerDependency in mock-data so the local version installed in this PR doesn't match the version on mock-data...

[EvanHahn]

I think it's time for us to make a new migration!

I think we plan to add this to a version of @mapeo/core that the MVP doesn't depend on--something like v1.1.0. Given that, I think we'll need a new migration here.

[EvanHahn]

Now that we've released @comapeo/[email protected], I think we can revisit this.

[tomasciccola]

@EvanHahn I'm having a couple of type errors on test-e2e/project-crud.js which I'm not sure how to interpret...

Also, the awana-lockfile-bot is showing a package-lock change with @mapeo/schema. I think we still have transitive dependencies on mock-data to mapeo/schema, could the type error be related to that (I don't think though...)

[tomasciccola]

I think something related to ts's structural typing is tripping us here. Since 'observation' and 'remoteDetectionAlert' both have a metadata field I think it expects remoteDetectionAlert.metadata to be the same as observation.metadata?
e.g. adding manualLocation to remoteDetectionAlert fixes all type errors... @EvanHahn any clue?

[tomasciccola]

So, after this PR was merged I updated the branch but I still get what is basically the same type error:
We have two schemas with a field with the same name ({observation,remoteDetectionAlert}.metadata).
It expects remoteDetectionAlert.metadata to have manualLocation which actuall belongs to observation.
I think I integrated the changes right (basically adding remoteDetectionAlert as a case in create, createWithMockData, update and getUpdatedFixture) but the issue still persists :'(

[EvanHahn]

This still needs a new migration (rather than deleting the old one), but I think is ready to go otherwise.

[awana-lockfile-bot]

package-lock.json changes

Click to toggle table visibility

Name	Status	Previous	Current
@comapeo/geometry		-	1.0.2
@comapeo/schema		1.0.0	1.1.1
@mapeo/mock-data		2.0.0	2.1.1
dereference-json-schema		-	0.2.1
protobufjs		7.2.5	7.4.0

[awana-lockfile-bot]

package-lock.json changes

Click to toggle table visibility

Name	Status	Previous	Current
@comapeo/geometry		-	1.0.2
@comapeo/schema		1.0.0	1.2.0
@mapeo/mock-data		2.0.0	2.1.1
dereference-json-schema		-	0.2.1
protobufjs		7.2.5	7.4.0