Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Enable forced update of community block schema when schema is not used yet #1781

Closed
hevp opened this issue Apr 16, 2020 · 0 comments · Fixed by #1802
Closed

Enable forced update of community block schema when schema is not used yet #1781

hevp opened this issue Apr 16, 2020 · 0 comments · Fixed by #1802

Comments

@hevp
Copy link
Member

hevp commented Apr 16, 2020

It's now not possible to update a community block schema with backwards incompatible changes, even though no records exist for the corresponding community.

Proposed change:

  • Add a flag '--force' to the relevant command to enforce the update of the block schema for the community, provided that no records exists using that particular block schema version
@hevp hevp changed the title Enable forced update of community block schema when no records are present Enable forced update of community block schema when schema is not used yet Apr 16, 2020
@hevp hevp mentioned this issue Mar 17, 2021
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update root schema hevp/b2share
1 participant
@hevp