I’m designing some custom races for my campaign and I’d like to allow large size characters. It seems that large characters are discouraged for some reason and although I’d like to know why what’s more important is finding some official rules or guidelines on how to create large character races like minotaurs, half-ogres, centaurs, etc.
I’ve got a basic understanding of accessibility and how it applies to visual elements of your product and I’m keen to apply guidelines as best as I can.
My question is does the hover state button text also need to comply with accessibility guidelines as well as the normal state?
I’m struggling about this topic for a while and I think I can’t wrap my head about the angular style naming conventions. My question is: why is everything called a service?
I’m a backend-guy, and in the backend I have – for example – a UserRepository which accesses the database and a UserService hich holds the business-logic. So I use the sufix “Repository” for a data access layer and “Service” for business logic.
Moving to angular, it confuses me that everything must be a service, according to the style guide. I would like to have a UserApiClient which connects to the api and a UserService which holds business logic.
In the same manner I would like to have a UserDetailsPage, UserNameComponent and UserEditForm instead of a “UserDetailsComponent”, “UserNameComponent” and “UserEditComponent”.
I would like to have more sufixes to structure the type of my classes then “service” and “component”.
By the way, I know that I can name my classes whatever I want – but it confuses me, that angular is so strict about this topic: the style guide ist very clear and the cli doesn’t event let me choose the sufix for my classes. Renaming everything manually after creating via cli or creating everything manually couldn’t be the answer…
Is this really a concern or do I just have to “accept” the style guide as it is…? Am I seeing things wrong or not “the angular way”?
Thanks for clearing this up!
C# extension methods have seen a rise in usage over recent years. The offical microsoft guidelines on usage state: “In general, we recommend that you implement extension methods sparingly and only when you have to” The extension method guidelines.
On the other hand Microsoft are now using them heavily in dot net core (see the microsoft extensions name space). This is particularly prevalent is asp core where the initializaion of the IServiceCollection is implemented in extension methods, for example see The service collection service extensions. Dot net core tutorials has an article listing this as a design pattern suggesting that it is best practice. Quite a few popular nuget packages also use this method to initialise services: Swagger is configured this way microsoft docs as well as mediatr their implementation
Should the guidelines be updated or should this practice be avoided? If the guidelines are to be updated what should they be?
I’m looking at the offical docs here
Why is it that when changing the preference of a class marked with
@api you can depend on a MAJOR version but when you change the preference of an interface marked with
@api you have to depend on a MINOR version release. Is it not kinda the same thing?
Same thing goes for implementing an interface (depend on MINOR) and extending a concrete class (depend on MAJOR) both marked with
What is the reasoning behind this?
IMHO implementing an interface should not make me more dependent of a module than extending a concrete class.
As options guidelines can be enabled and disabled. There is no option to add guidelines neither help about it.
It’s a well established recommendation for publications containing masses of continuous text to use hyphenation.
Are there any ideas or guidelines on how hyphenation should be (not) used on interactive elements of UI or those that do not represent part of text content? For example, when designing 1) a menu 2) sitemap 3) sidebar etc.
The search didn’t give me anything on this subject. I think mainly of web interfaces here but it may be interesting how this may be applied to app design too.
My question is if everything is suppose to be in 4px or 8px increments does that mean even the height of sections or containers? For instance if you wanted to have a section that filled the viewport you would set that section to 100vh. However that would break the baseline grid. I’m just confused because some of the guidelines seem to be counterproductive to responsive design. For instance setting an exact container / section height would mean resizing them all at specific breakpoints.
We develop an app for staffing company. Our app is basically used to mark attendance for that particular organisation. But when i upload app to the apple store then every time app store reject it and mansion that it is not custom app. Please help me if any developer had face that issue.
I’m new to certification arguments. I have an issue with a requirement that is to make an application in a certified Windows 2008 environment.
What are / where can I find a guide to WS2008 CC-compliant setup: which features can I safely install and which I shouldn’t (so I have a system on which I could do some tests and ‘touch’ the features available).