Skip to content

build: switch to yaml file for size test golden #19621

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
merged 2 commits into from
Jun 13, 2020

Conversation

devversion
Copy link
Member

Switches the size-test golden from a JSON file to a Yaml
file. The motivation is that JSON files quickly can result
in merge conflicts. This is mostly because of trailing commas
that need to be added when new entries are added to the size-test
golden. This should be improved with YAML where a new entry can
be added without having to change existing ones.

Note: Marking as P2 because it would be good to get that in before I start sending more individual PRs for other components affected by light-weight tokens.

@devversion devversion added P2 The issue is important to a large percentage of users, with a workaround merge safe target: patch This PR is targeted for the next patch release labels Jun 12, 2020
@devversion devversion requested review from jelbourn and a team as code owners June 12, 2020 08:47
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 12, 2020
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels Jun 12, 2020
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

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

@andrewseguin
Copy link
Contributor

Please rebase

For consistency with other size-tests's we are going to add,
we should move the nav-list one into a folder that is
dedicated for list size tests.
Switches the size-test golden from a JSON file to a Yaml
file. The motivation is that JSON files quickly can result
in merge conflicts. This is mostly because of trailing commas
that need to be added when new entries are added to the size-test
golden. This should be improved with YAML where a new entry can
be added without having to change existing ones.
@devversion devversion force-pushed the build/improve-size-golden branch from 13c1fa0 to b997d45 Compare June 12, 2020 23:47
@andrewseguin andrewseguin merged commit a3dabc9 into angular:master Jun 13, 2020
andrewseguin pushed a commit that referenced this pull request Jun 13, 2020
* build: move nav-list size-test into dedicated `list` folder

For consistency with other size-tests's we are going to add,
we should move the nav-list one into a folder that is
dedicated for list size tests.

* build: switch to yaml file for size test golden

Switches the size-test golden from a JSON file to a Yaml
file. The motivation is that JSON files quickly can result
in merge conflicts. This is mostly because of trailing commas
that need to be added when new entries are added to the size-test
golden. This should be improved with YAML where a new entry can
be added without having to change existing ones.
@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 Jul 14, 2020
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 P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants