-
Notifications
You must be signed in to change notification settings - Fork 4k
Copy amp-story 1.0 back to 0.1 #14626
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big deal, but if you want to preserve your github own line contributions numbers, you can commit with a diff author
git commit --author="Delicious copy pasta <copy@pasta.org>"
|
@gmajoulet I think that might fail the CLA check? |
|
Added @jridgewell to take a look for the change to the bundle size (baf2670) |
| * @param {!Window} win | ||
| * @return {?Promise<?../extensions/amp-story/0.1/variable-service.StoryVariableDef>} | ||
| */ | ||
| static storyVariableServiceForOrNullV01(win) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we reuse the same services, passing in an optional parameter for the version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be pretty complicated since the services' functions return different types, so we'll have to change every usage downstream
* Initial copy of 1.0 => 0.1 * Create separate services for v0.1 * Update 0.1 tests to use 0.1 services * Increase uncompiled bundle size from 334.46kb to 334.55kb * Wrong version for system-layer tests * Update inline styles for page scaling to new API
This is the second step of #14357: removing the alias from 0.1=>1.0, and instead having separate codebases for each. This is necessary to hold breaking changes in 1.0 until later (since, if they were aliased, any breaking changes in 1.0 would also go. to 0.1).
Note that git won't hint these files, since it's not a move. Also note that a separate copy of the service getters had to be made, since the implementations are different types (see 07fd2fd).