vf-graphql issueshttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/issues2019-05-12T17:15:23Zhttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/issues/26Finalise schema for agreements2019-05-12T17:15:23ZpospiFinalise schema for agreementsCurrently the codebase has `ExchangeAgreement`, but not `Agreement`, which keeps getting mentioned. These are parts of external vocabularies, but which ones? We (probably) need to bring the fields into GraphQL for completeness. And I'm u...Currently the codebase has `ExchangeAgreement`, but not `Agreement`, which keeps getting mentioned. These are parts of external vocabularies, but which ones? We (probably) need to bring the fields into GraphQL for completeness. And I'm unsure whether `Agreement` is the only record we should have, or if both `Agreement` & the more specific `ExchangeAgreement` are needed?
I also note that the current status of GraphQL is that:
- `EconomicEvent`s, `Commitment`s, & `Intent`s can be created under an agreement
- `Fulfillment`s can be created under agreements, but `Satisfaction`s cannot
- `Transfer`s can't be created under an agreement, but it looks like they should be able toLynn FosterLynn Fosterhttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/issues/21Flesh out mutations2021-12-13T09:43:33ZpospiFlesh out mutationsNeed to figure out what requirements exist here and define appropriate methods- the coverage that's come in from NRP is patchy.Need to figure out what requirements exist here and define appropriate methods- the coverage that's come in from NRP is patchy.Lynn FosterLynn Fosterhttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/issues/20Verify `inScopeOf`2019-05-03T02:53:48ZpospiVerify `inScopeOf`I've gone through and put this on basically every object except for `Agent`s & their role-based records. Just confirming that's correct, and that it *should* be applied to things like `ResourceSpecification`, which may not be things we'd...I've gone through and put this on basically every object except for `Agent`s & their role-based records. Just confirming that's correct, and that it *should* be applied to things like `ResourceSpecification`, which may not be things we'd want to limit by scope.
If it all looks good you can just close this issue (;Lynn FosterLynn Foster