Skip to content

build: run custom tslint rules on new packages #17033

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

Merged

Conversation

devversion
Copy link
Member

@devversion devversion commented Sep 10, 2019

Apparently we didn't run the custom tslint rules for the new packages
that have been merged (youtube-player and google-maps). This is
because we have a whitelist of packages we want to run these custom
lint rules against.

It should be actually the other way around where we only specify the folders
we don't want to lint against. That way, new folders are automatically linted
and we need to explicitly exclude them if we don't want to run for those.

Note: Marked as target minor because it will not merge safely into the patch branch (as youtube-player is not part of that branch).

I'm not sure if the module.id is technically needed for those packages (not sure if they are synced into g3), but we should add them for now to satisfy the validate-decorators lint rule. We can remove them as part of the overall cleanup with #13883

Apparently we didn't run the custom tslint rules for the new packages
that have been merged (`youtube-player` and `google-maps`). This is
because we have a whitelist of packages we want to run these custom
lint rules against.

It should be actually the other way around where we only specify the folders
we _don't_ want to lint against. That way, new folders are automatically linted
and we need to explicitly exclude them if we don't want to run for those.
@devversion devversion added the target: minor This PR is targeted for the next minor release label Sep 10, 2019
@devversion devversion requested review from jelbourn and a team as code owners September 10, 2019 12:15
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 10, 2019
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I think its the right decision to include the module.id typings for now. They are not currently synced into g3, but I am unsure if this is expected to change as they go stable.

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 10, 2019
@jelbourn jelbourn added target: patch This PR is targeted for the next patch release and removed target: minor This PR is targeted for the next minor release labels Sep 12, 2019
@jelbourn
Copy link
Member

Changed to patch since we released a minor

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn merged commit 0d7e038 into angular:master Sep 12, 2019
jelbourn pushed a commit to jelbourn/components that referenced this pull request Sep 24, 2019
Apparently we didn't run the custom tslint rules for the new packages
that have been merged (`youtube-player` and `google-maps`). This is
because we have a whitelist of packages we want to run these custom
lint rules against.

It should be actually the other way around where we only specify the folders
we _don't_ want to lint against. That way, new folders are automatically linted
and we need to explicitly exclude them if we don't want to run for those.

(cherry picked from commit 0d7e038)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants