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.

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

dynamically rename xmlns if different urls shares the same xmlns #31

Open
Xiaoy312 opened this issue Jan 19, 2022 · 2 comments
Open

dynamically rename xmlns if different urls shares the same xmlns #31

Xiaoy312 opened this issue Jan 19, 2022 · 2 comments
Labels
kind/enhancement New feature or request. triage/untriaged Indicates an issue requires triaging or verification.

Comments

@Xiaoy312
Copy link

Xiaoy312 commented Jan 19, 2022

What would you like to be added:

dynamically rename xmlns if different urls shares the same xmlns:

  • file1.xaml: xmlns:local="using:Something.This"
  • file2.xaml: xmlns:local="using:Something.That"

the rename should cover:

  • node name: <local:MyControl />
  • certain attribute values:
    • mc:Ignorable
    • [Style or ControlTemplate].TargetType
    • Binding.Path: <TextBlock Text="{Binding Path=(ext:MyExtensions.SomeProperty)}" />

with options to omit/override specific xmlns for edge-case scenarios: (like uno-reserved xmlns: win, not_win, ios, etc...)

@Xiaoy312 Xiaoy312 added kind/enhancement New feature or request. triage/untriaged Indicates an issue requires triaging or verification. labels Jan 19, 2022
@jeromelaban
Copy link
Member

For now, the tool marks namespaces as invalid duplicates, which avoids invalid cases where some namespaces could be ignored.

@MatFillion
Copy link

MatFillion commented Apr 7, 2022

this case happened in 3 of the 3 projects who added xaml-merge. (for xmlns specificall)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request. triage/untriaged Indicates an issue requires triaging or verification.
Projects
None yet
Development

No branches or pull requests

3 participants