Closed cosad3s closed 3 months ago
This issue happens because we maintain the state by saving it in local storage. Simply deleting the local storage should fix this issue.
Oh that's it! Indeed, I have deleted the local storage and the heatmap is correctly updated! Thanks! 💯
So maybe there is something to improve there about LocalStorage update regarding the meta.yaml
configuration?
This issue has been automatically marked as stale
because it has not had recent activity. :calendar: It will be closed automatically in one week if no further activity occurs.
This issue was closed because it has been stalled for 7 days with no activity.
Can we please re-open this issue? Being able to set team names that match an organisation is vital for adoption of the DSOMM as a viable tool.
I have added to my
meta.yaml
custom team:And for
generated.yaml
, I tried to:teamsImplemented
The docker image is launched with
docker run -v $(pwd)/meta.yaml:/srv/assets/YAML/meta.yaml -v $(pwd)/generated.yaml:/srv/assets/YAML/generated/generated.yaml -p 8080:8080 wurstbrot/dsomm
The heat map seems always to be empty / uneditable, except if the teams are named "A", "B" (default teams), etc.