coc-metalsupdates itself, right? @ckipp01
CocInstall coc-metalsit doesn't do it automatically anymore
coc-metalsversion is, I probably ned to update that via
CocUpdateis what you're saying?
@ckipp01 I mean that previously, metals/vscode would do auto imports for me, for example in one file it would look like this:
package com.geomoby.mozambique import com.geomoby.mozambique.model.Common.Point
...Common.Point is also in
com.geomoby.mozambique but maybe in another sub-project, but then suddenly I found myself with lots of errors, saying that
Common.Point is not in package
com.geomoby.mozambique.com.geomoby.mozambique, and the imports had to be changed to
package com.geomoby.mozambique import _root_.com.geomoby.mozambique.model.Common.Point
Ultimately that's not a huge problem, but it was a strange phenomenon.
Why is the compiler complaining that id in the second line is unused,
when it is used in the third line?
for(party <- da.participantParty; id <- party.party.partyIdentification; if(id.id.schemeId.getOrElse("?") == ui.App.app.company.get.schemeId)) yield party
participantParty and partyIdentification are both lists