Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Enhancements #3

Open
redonkulus opened this issue Jan 17, 2020 · 2 comments
Open

Possible Enhancements #3

redonkulus opened this issue Jan 17, 2020 · 2 comments
Assignees

Comments

@redonkulus
Copy link

@pankajparashar-zz @src-code

I know this extension hasn't been touched in a while but we would like to use it more within Yahoo. A couple of enhancements to consider:

  • Do not require a root level atomizer.json file. In our project setups, the atomizer file is typically in a nested directory. We cannot rely on it being at the root. Ideally, this extension wouldn't need any activation event besides when a user is editing in one of the defined snippet files.
  • Support more snippet languages. Not sure if this works, but we use marko for templating and it would be good to have access to the extension when modifying the file.
  • Ensure extension is using latest ruleset from the atomizer NPM package. The snippets list is static today, would be nice to generate this at build time.
@renato-dawnlight
Copy link

@redonkulus I'm thinking about ressurrecting this. I'm interested in using this again. Have you guys had the chance to look at these?

@redonkulus
Copy link
Author

@renato-dawnlight please enhance, I haven't had a chance to come back to this. But we love to have it updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants