SL23W52: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
<br /> | <br /> | ||
* '''Update dynmap,''' Invalid texture block name: minecraft:air | *'''Update dynmap,''' Invalid texture block name: minecraft:air | ||
* '''Creating a new pod with a uuid key via copy/paste invites mistakes even if we use a UUID wrapper like DocId/LayoutId as:''' | *'''Creating a new pod with a uuid key via copy/paste invites mistakes even if we use a UUID wrapper like DocId/LayoutId as:''' | ||
** PodType.X can still reference the old pod | **PodType.X can still reference the old pod | ||
** manager.addInternal()... can still reference user.getXPod(XId.of(uuid, nickname) | **manager.addInternal()... can still reference user.getXPod(XId.of(uuid, nickname) | ||
** In both cases the assumed type-safety by the Id-wrapper does not help us | **In both cases the assumed type-safety by the Id-wrapper does not help us | ||
**'''After that saving will actually work, as in both cases we just convert a java object to json automatically,''' probably should have a type checking in the pod-system to make sure this cannot happen | |||
Revision as of 13:34, 26 December 2023
- Update dynmap, Invalid texture block name: minecraft:air
- Creating a new pod with a uuid key via copy/paste invites mistakes even if we use a UUID wrapper like DocId/LayoutId as:
- PodType.X can still reference the old pod
- manager.addInternal()... can still reference user.getXPod(XId.of(uuid, nickname)
- In both cases the assumed type-safety by the Id-wrapper does not help us
- After that saving will actually work, as in both cases we just convert a java object to json automatically, probably should have a type checking in the pod-system to make sure this cannot happen