-
Notifications
You must be signed in to change notification settings - Fork 154
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
how to do similar plantuml support for Power Platform icons #42
Comments
Thank you for opening this issue. Great question! My first impulse is to say "separate repo", especially if we take into account that we'd want to do the same thing with other icon sets (for instance Microsoft Dynamics 365 icons) But if we want to use the same approach, we'll also want to use the same automation. That would mean either duplicating the build scripts to multiple repos, or moving them into a separate project as well. At that point, we might be better of "just" adding them here, but in that case the project name "Azure-PlantUML" is no longer correct, which would mean a rename (for instance to "Microsoft-PlantUML"). Or we could make a "Microsoft-PlantUML" repo anyway, which would include this repo and other (yet to be created) repos. I'll have to think about it some more, but I am all for making sure the Microsoft Power Platform icons are also made available to PlantUML! Maybe some of the @plantuml-stdlib/maintainers have some thoughts about this? |
Thanks @Potherca, |
At this point, I'm leaning heavily towards splitting the The Power Platform icons would be a new repository without Once everything works, the Any decisions regarding a "Microsoft-PlantUML" could then be postponed until later. |
We are also working in as dynamics environment combination with azure amd would highly benefit of having those components |
Is it possible to use this project to also include these icons? separate repo? same approach?
https://docs.microsoft.com/en-us/power-platform/guidance/icons
Thanks & Regards,
Stefan
The text was updated successfully, but these errors were encountered: