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

Should LegacyWindowAlias and LegacyNamespace be allowed together? #645

Closed
Ms2ger opened this issue Feb 13, 2019 · 1 comment
Closed

Should LegacyWindowAlias and LegacyNamespace be allowed together? #645

Ms2ger opened this issue Feb 13, 2019 · 1 comment

Comments

@Ms2ger
Copy link
Member

Ms2ger commented Feb 13, 2019

No description provided.

@domenic
Copy link
Member

domenic commented Feb 15, 2019

Let's say no. They're not currently, and ideally they should not be used in the future.

@domenic domenic mentioned this issue Feb 22, 2019
Merged
Ms2ger added a commit that referenced this issue Feb 25, 2019
@Ms2ger
Disallow combining LegacyWindowAlias and LegacyNamespace
5da20cf 
This doesn't currently happen, and we don't expect it to happen in the future.

Fixes #645.
@Ms2ger Ms2ger mentioned this issue Feb 25, 2019
Merged
Ms2ger added a commit that referenced this issue Feb 25, 2019
@Ms2ger
Disallow combining LegacyWindowAlias and LegacyNamespace
27afa8c 
This doesn't currently happen, and we don't expect it to happen in the future.

Fixes #645.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ms2ger @domenic