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

The class Range is not handled by the migration tool #30

Closed
hesara opened this issue Apr 18, 2017 · 0 comments · Fixed by #31
Closed

The class Range is not handled by the migration tool #30

hesara opened this issue Apr 18, 2017 · 0 comments · Fixed by #31

Comments

@hesara
Copy link
Contributor

hesara commented Apr 18, 2017

The package name was changed in Vaadin 8 from com.vaadin.shared.ui.grid.Range to com.vaadin.shared.Range but the migration tool does not update it.
hesara pushed a commit that referenced this issue Apr 19, 2017
Rename irregularly changed classes
b4e8b59 
This change updates package paths for the classes Range and PropertyId,
which do not follow the standard pattern of prepending v7.

Fixes #27, fixes #30
@hesara hesara mentioned this issue Apr 19, 2017
Merged
@ahie ahie closed this as completed in #31 Apr 19, 2017
ahie pushed a commit that referenced this issue Apr 19, 2017
@hesara @ahie
Rename irregularly changed classes (#31)
f7d41ff 
This change updates package paths for the classes Range and PropertyId,
which do not follow the standard pattern of prepending v7.

Fixes #27, fixes #30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rename irregularly changed classes vaadin/framework8-migration-tool
1 participant
@hesara