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

Project Ideas #702

Open
ksdme opened this issue Jan 31, 2019 · 3 comments
Open

Project Ideas #702

ksdme opened this issue Jan 31, 2019 · 3 comments

Comments

@ksdme
Copy link
Member

ksdme commented Jan 31, 2019

Here are a couple of interesting ideas I had:

  • Standardising .coafile syntax for starters using YAML.
  • Build .coafile plugins for major code editors with support for features like autocomplete.
  • Building on the above idea, a tool to port specific linter configurations to coala configurations.
  • A repository of standard coala linter configurations, probably built using the above tool and running it on standard code repositories.
  • A tool like https://goreportcard.com with shields.io integration for badges.
@utkarsh2102
Copy link
Member

Can we fairly integrate any of them with LSP?

@Naveenaidu
Copy link
Member

Naveenaidu commented Feb 3, 2019

@ksdme

* Standardising .coafile syntax for starters using YAML.

Can you please explain what do you actually mean by standardizing. Do you mean something like a moban, coala uses to maintain standardised code. Or does it mean to provide a YAML file to the users where they can enter their values and the .coafile gets generated automatically?

I was thinking of creating a moban template for .coafile in the coala repository and then they can run moban to apply the templates. Is this what the above point means?

    * Building on the above idea, a tool to port specific linter configurations to coala configurations.

Can you please expand on this idea.

@PrajwalM2212
Copy link
Member

PrajwalM2212 commented Feb 3, 2019

@Naveenaidu I think Standardising .coafile syntax for starters using YAML. is something like #705.

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

No branches or pull requests

5 participants