search

simondotm / beeb-vsc

Visual Studio Code Extension to support code development for BBC Micro
https://marketplace.visualstudio.com/items?itemName=simondotm.beeb-vsc
MIT License
14 stars 3 forks source link

Can we simplify the error parsing feature? #101

Closed simondotm closed 7 months ago

simondotm commented 8 months ago

Clearly, some folks have some exotic workspace setups for their beeb projects! 😂

If it is at all possible for the extension to determine entry points from any beebasm command lines in the tasks.json and then somehow automatically figure out include dependencies from that root without users having to manually manage it, that would be great.

Let's discuss.

Originally posted by @simondotm in https://github.com/simondotm/beeb-vsc/issues/99#issuecomment-2021304354

tommy9 commented 8 months ago

For safety, should probably be able to scan both the older 0.1.0 schema and new 2.0.0 schema, in case some people created updated tasks.json files themselves.

simondotm commented 8 months ago

Originally posted by @tommy9 in https://github.com/simondotm/beeb-vsc/issues/99#issuecomment-2021352383

I agree that picking up the entry points from the existing tasks.json would be a really nice thing to do automatically. I had avoided it earlier because of the number of projects relying on exotic batch scripts or make files but that isn't a reason not to add this quality of life feature for the many standard projects that are out there.

Ah yes, I remember the other stardot thread now, the folks with the makefiles and batch files, yes, that makes things spicier.

Still, I think if at least we could implement the automation of parsing the hierarchy of includes somehow, then settings.json content could be just a list of entry files rather than all included files perhaps?