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

Determine how package managers beyond npm are handled #2

Open
CharlieGreenman opened this issue Jan 11, 2023 · 1 comment
Open

Determine how package managers beyond npm are handled #2

CharlieGreenman opened this issue Jan 11, 2023 · 1 comment

Comments

@CharlieGreenman
Copy link
Contributor

CharlieGreenman commented Jan 11, 2023

E.g. for cargo.toml for Rust how would we handle that?

The current coreProgrammingLanguagesMap syntax of e.g.

export function coreProgrammingLanguagesMap() {
  return {
    '@angular/core': 'angular',
    'react': 'react',
    'vue': 'vue',
    'svelte': 'svelte',
    'aws-sdk': 'aws',
    'typescript': 'typescript'
  }
}

Would not work for this

@CharlieGreenman
Copy link
Contributor Author

CharlieGreenman commented Jan 11, 2023

Hmm, i think what would make sense is that we have all ways of versioning things within a switch case statement for each programming language. Then let that fan out. If it exists then will pick it up. This will work. I will get this in the code base sooner than later. E.g.

  switch(packageManager) {
     'package.json': 
        //do npm stuff
      'cargo.toml`: 
        //do rust stuff  
  }

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

1 participant