-
Notifications
You must be signed in to change notification settings - Fork 19
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
Introduce linter for Typescript code #32
Comments
Can I work on this issue? |
/assign @VamshiReddy02 |
/assign |
I am intentioanally breaking lint ; in order to test yarn backstage-cli repo lint --since origin/main script .. No matter how many times i tried, i am getting successfull lint builld.. This one is yarn backstage-cli repo lint, is checking lint for all the project .. @aliok |
@ahmetcihank let's start with using What do you think? |
@aliok sounds good, thanks a lot. I am assuming there is something about packages , which i couldn't figure out . |
* added catalog api pagination(#28) * added test case & initialized cursor(#28) * changed cursor into local variable(#28) * introduced query limit constant & fixed tests (#28) * test case added (#28) * pagination test case extended * linting actions added in pr&release steps (#32) * fixed path (#32) * checkout added (#32) * dependency action added (#32) * refactoring for lint issues (#32) * refactoring for lint issues (#32) * revert package json changes (#32) * fixed linting issues (#32) * fixed linting (#32)
/close |
@aliok: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Typescript code is not linted currently.
Notes:
lint
scripts in package.json:backstage-plugins/backstage/package.json
Lines 22 to 23 in 84b0e1c
lint
andlint:all
do. Need to understand the difference and pick the correct one.release
andrelease-snapshot
) to run the linterSo, we should have a separate linter action that is to be run in every PR AND we should also run the linter in the release actions as we double check everything when we release.
The text was updated successfully, but these errors were encountered: