Closed ailisp closed 1 year ago
@near-akaia-root Please review this one. Thanks!
The schema I planned to apply is more complicated ( it includes community -> integrations -> github ) but this temporary solution is ok too, given it's dead simple
Yeah I see your future plan to save everything about community in a json, which should be fit the SocialDB. For now let's keep the contract to storing most field structured and github board configuration as json
Should be a good temporary solution for now, before we moving away from contract based approach. Still use
edit_community
to modify github field of a community. JSON is unchecked but given only community admins can edit it, and they would do it from UI, we can assume valid format of board configuration is stored.Since we have not store any community in production contract, migration part is unchanged.