* fancy autocomplete that
* writes little next obvious bits
* can write architecture and code review Markdown docs complete with Mermaid diagrams which look super cool in the rendered .md file on the site or VS Code’s Preview,
* small refactorings
* fancy autocomplete that
* writes little next obvious bits
* can write architecture and code review Markdown docs complete with Mermaid diagrams which look super cool in the rendered .md file on the site or VS Code’s Preview,
* small refactorings
* Move responsibility
* Extract responsibility
* Inline responsibility
* Extract role
* Inline role
* Move responsibility
* Extract responsibility
* Inline responsibility
* Extract role
* Inline role
foojay.io/today/ide-fo...
#Java #NetBeans #MCP
foojay.io/today/ide-fo...
#Java #NetBeans #MCP
- Move Responsibility
- Extract Responsibility
- Inline Responsibility
- Extract Role
They all preserve any realised outcomes from the spec.
- Move Responsibility
- Extract Responsibility
- Inline Responsibility
- Extract Role
They all preserve any realised outcomes from the spec.
BUT this only works if you obey certain very strict rules:
- No import.meta.glob or reading source code file positions at runtime
- No global state
Probably not possible the more I think about it
BUT this only works if you obey certain very strict rules:
- No import.meta.glob or reading source code file positions at runtime
- No global state
Probably not possible the more I think about it
Obviously doesn't work for new features. Might not even work for bugfixes. But it might enable a class of refactorings that help us all make changes more confidently.
Obviously doesn't work for new features. Might not even work for bugfixes. But it might enable a class of refactorings that help us all make changes more confidently.
The lesson:
Good automation doesn’t replace judgment. It makes intent explicit.
go.dev/blog/interac...
#Golang #DevTools
The lesson:
Good automation doesn’t replace judgment. It makes intent explicit.
go.dev/blog/interac...
#Golang #DevTools
gopls v0.24.0 refactorings can now ask you questions first. It relies on a proposed LSP change, which decides whether your editor gets it.
gopls v0.24.0 refactorings can now ask you questions first. It relies on a proposed LSP change, which decides whether your editor gets it.
go.dev/blog/interac...
This one is less about Go lang, but more about the new LSP capabilities to do interactive refactors with multiple params. This is more about the extension of the LSP protocol. So, so, so powerful!
#lsp #golang
go.dev/blog/interac...
This one is less about Go lang, but more about the new LSP capabilities to do interactive refactors with multiple params. This is more about the extension of the LSP protocol. So, so, so powerful!
#lsp #golang