search

jacamo-lang / jacamo-web

web interface for JaCaMo
7 stars 6 forks source link

Issues awareness #21

Closed TimKam closed 4 years ago

TimKam commented 4 years ago

Develop issue awareness UI

cleberjamaral commented 4 years ago

We can split it into two reporting functions: 1) When trying to push his version, notice the current developer that there are errors/warnings (Maybe he is ignoring those ones when he was editing some agent or it just happened after another developer push some change in a related agent) 2) Provide a way to make other developers aware of issues that become open after the last push. Maybe we could have a window to show these open issues.

cleberjamaral commented 4 years ago

Format: issues = [ { level: 'warning', message: 'lorem ipsum' }, { level: 'hint', message: 'lorem ipsum' }, { level: 'error', message: 'lorem ipsum' } ]

cleberjamaral commented 4 years ago

Basic /lock and /unlock end-points are available. Closes #26

cleberjamaral commented 4 years ago

The websocket endpoint could be used for this purpose. The current format is in plain text saying "developedName locked resourceName". Indeed, a list of messages is maybe not suitable at this time because the messages are pushed directly to all opened ws connections (no buffering).

cleberjamaral commented 4 years ago

Since we now have an interface that shows the user open issues before committing, I am closing this issue.