Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Expose is_assignable to determine if one view can be assigned to another #1936

Closed
AndrewGaspar opened this issue Dec 11, 2018 · 1 comment
Closed

Expose is_assignable to determine if one view can be assigned to another #1936

AndrewGaspar opened this issue Dec 11, 2018 · 1 comment
Assignees
@crtrott @jeffmiles63
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
Milestone: Release 3.1

Comments

@AndrewGaspar
Copy link
Contributor

Briefly discussed in #1594. Essentially we just need to be able to test if array A can be successfully assigned to array B.
@ndellingwood ndellingwood added the Enhancement Improve existing capability; will potentially require voting label Feb 1, 2019
@ndellingwood ndellingwood added this to the 2019 April milestone Feb 7, 2019
@crtrott crtrott removed this from the 2019 April milestone Aug 21, 2019
@jeffmiles63 jeffmiles63 added this to the Tentative 3.1 Release milestone Aug 28, 2019
@jeffmiles63 jeffmiles63 added this to To do in Milestone: Release 3.1 via automation Aug 28, 2019
@jeffmiles63 jeffmiles63 mentioned this issue Mar 4, 2020
Closed
@crtrott crtrott self-assigned this Mar 19, 2020
@crtrott
Copy link
Member

crtrott commented Mar 19, 2020

Addressed through #2874

@crtrott crtrott closed this as completed Apr 14, 2020
Milestone: Release 3.1 automation moved this from To do to Done Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@crtrott crtrott

@jeffmiles63 jeffmiles63

Labels
Enhancement Improve existing capability; will potentially require voting
Projects
No open projects
Milestone: Release 3.1
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@AndrewGaspar @crtrott @ndellingwood @jeffmiles63