Skip to content
This repository has been archived by the owner on Aug 22, 2021. It is now read-only.

Remove Polymer references from installation instructions #203

Merged
merged 1 commit into from May 16, 2019

Conversation

samiheikki
Copy link
Contributor

Connects to https://github.com/vaadin/components-team-tasks/issues/420

I can create same PR to all components as well once this is merged

@web-padawan
Copy link
Member

No need to submit PRs for each component. We usually review the PR in skeleton, and then push to master manually. Also, please add [skip ci] to commit message.

@samiheikki
Copy link
Contributor Author

Added [skip ci] to commit msg

@lkraav
Copy link
Contributor

lkraav commented Apr 1, 2019

Can you guys enlighten me what https://github.com/vaadin/components-team-tasks/issues/420 is all about? (private repo)

What's the usefulness of this change across components?

@samiheikki
Copy link
Contributor Author

@tomivirkki can you share details for @lkraav

@web-padawan
Copy link
Member

@lkraav the overall idea is that in future, we should iteratively move away from Polymer library (which is not recommended for using in new projects by Polymer team).

Until then, we would like to update docs so the users don't mistakenly associate Vaadin components with Polymer Elements, which are in the maintenance mode. I agree this change is rather a compromise but it also indicates that we at least acknowledge the need for updating our technology stack.

@web-padawan web-padawan merged commit e630bf0 into master May 16, 2019
@web-padawan web-padawan deleted the fix/remove-polymer-mentions branch May 16, 2019 08:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants