https://pantsbuild.org/ logo
Join Slack
Powered by
Fun little Sunday project results. Apparently crea...
# general
w
Fun little Sunday project results. Apparently creating a VSCode extension is wayyyy easier than I had previously assumed 🙂 Monitoring my source roots and transitive targets in the VS Code sidebar
❤️ 7
😮 1
❗ 4
👀 2
b
I hope you open source that! 🙏
w
Yep, without the BSP its kinda meh, but it just calls to the pants script and its decent enough for what i need to visualize without constantly running terminal commands
As requested: https://github.com/robotpajamas/suspenders Also, @busy-vase-39202 I just realized I used the Pants logo without express permission - but I guess it was under the implicit understanding that whenever this plugin becomes half-decent, it gets pulled into the 
pantsbuild
organization and out of my org - so we have people to maintain it.
If anyone has any ideas of what they think could be simple enhancements to the IDE plugin (noting that I haven't integrated the BSP, so "very simple" is probably more like it)... Feel free to create an issue here https://github.com/RobotPajamas/suspenders/issues My focus is on introspection, because I think it's useful but not worth constantly typing the commands in. However, the treeview on the left will have stuff like "package this target", "test this target", etc
h
This is seriously great! People have been asking for better VSCode support for a long time
w
My "let me make something to make my life marginally easier" nature plays out well in open source communities 🙂
❤️ 2
b
Love extensions like this. Makes me wanna eat em up. Nom nom nom. My maintainer 2c is we should probably consider the lifecycle of an "official" extension, as undoubtedly it'll see many changes as it grows and matures.
Ownership is another concern. As we onboard more cool and exciting things (yay) we should be prepared to own it. Right now I have no idea how we'd own this (although I'm personally very interested) in terms of CI/CD, branching+release, etc...
w
For sure, which is why it's living in one of my orgs right now - so much more to actually releasing software than just building it - that's like 50%
b
That question seems like potentially a good topic for next week's meetup...?
✅ 3
b
Last time I released a VS Code extension (a few years back) it wasn't too crazy. I'd be happy if this was published. I'd likely install and try it out. We should probably just be mindful of namesquatting on "Pants" or whatever
w
We should probably just be mindful of namesquatting on "Pants" or whatever
Currently robotpajamas.suspenders 🙂
👀 1
🙌 1
✅ 1
b
On a particularly slow day, I might look into BUILD file language support
w
I was looking into that and pants.toml support, but I wasn't really sure how they're natively working. For the Pants.toml validation, looks like you need a toml extension. Language support is possible, but I was assuming that would be rolled in with the experimental-bsp (which hopefully relates to lsp stuff) - with the goal of not re-doing that which is already in progress
b
I don't think there's any ongoing work for Python bsp. Additionally, I'm not sure vs code supports a Python bsp (I think it's still suuuper young over at jetbrains). Lastly, it'd be purely lsp, likely just piggy-backing off the existing pyright lsp support
w
aahh, okay okay, I thought IDE integration via the BSP would include LSP and was actively in prog. Cool beans
Mind creating a ticket for it?
b
✅
❤️ 1
b
Are there questions y'all have for JetBrains about the roadmap on this? Happy to track down someone in JetBrains devrel to pass that forward to.
b
I got involved on some issue somewhere. But Idk when I'll realistically have the time to learn the Python BSP 🙂
4 Views
Open in Slack
PreviousNext
Powered by