You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2024. It is now read-only.
We're looking for contributors who can help maintain this extension. Right now contributions come from me or some others who have a bit of time. There are some great bugs being reports but there's not much time to act on them.
Where can I contribute?
Respond to issues
Responding to issues is another extremely effective way to help out. I've set up an issue template to help make it easier to narrow down where problems are arising from. We would need someone who can try out bugs, test if there's enough information in the issue and help triage the problem.
Updating syntax highlighting
We have a contributing guide which helps you debug syntax highlighting issues and how to reproduce them.
Updating intellisense
We have a contributing guide which goes into more detail on how the intellisense works and where you can make changes. We mainly rely on sub-dependencies for this points you in the right direction.
Documentation
The documentation may not be up to scratch or suitable for newcomers. So any help here is also useful.
That’s great to hear @arsinclair. Feel free to ping me on here or in discord, it’s mainly just attacking the issues already posted. I don’t have time to maintain this repo anymore but I can help with merges/releases etc.
the contributing guide should be enough to get you started
@jasonwilliams sounds good! I might only be able to find time on weekends, but that's better than nothing 😁. I'm happy to become a co-maintainer (so, merges/releases) in case you don't have time. We can have a quick video call, if necessary.
I'm thinking of going through a backlog of bug reports first, but then also looking at implementing the auto-formatting of the styled code, this is something that I personally lack a lot.
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
We're looking for contributors who can help maintain this extension. Right now contributions come from me or some others who have a bit of time. There are some great bugs being reports but there's not much time to act on them.
Where can I contribute?
Respond to issues
Responding to issues is another extremely effective way to help out. I've set up an issue template to help make it easier to narrow down where problems are arising from. We would need someone who can try out bugs, test if there's enough information in the issue and help triage the problem.
Updating syntax highlighting
We have a contributing guide which helps you debug syntax highlighting issues and how to reproduce them.
Updating intellisense
We have a contributing guide which goes into more detail on how the intellisense works and where you can make changes. We mainly rely on sub-dependencies for this points you in the right direction.
Documentation
The documentation may not be up to scratch or suitable for newcomers. So any help here is also useful.
Join the Discord
Its a new server but it provides a central place people can come and ask questions. Please join
Any contributions are appreciated, feel free to reply here or join the discord above.
💅 ✨
The text was updated successfully, but these errors were encountered: