Is there a way to have multiple aliases, but to use as: acronym for one of them, something like this, but that actually works :smiley: alias Guard.Rbac.{Cache, RoleBindingIdentification, as: RBI}

What you show in best case could work as: alias Guard.Rbac, as: RBI alias Guard.Rbac.{Cache, RoleBindingIdentification} That’s because opts are on same level as other aliases. Alternatively Elixir could support this: alias Guard.Rbac.{Cache, {RoleBindingIdentification, as: RBI}} However this lo…

[image] Eiji: alias ParentName.{ {ChildA, as: A}, ChildB, {ChildC, as: C} } This is exactly what I meant :smiley: I dont agree that this is ‘ugly looking’. Elixir already supports this notation: alias ParentName.{ ChildA, ChildB, ChildC } and I don’…

[image] VeljkoMaksimovic: alias Guard.Rbac.{Cache, RoleBindingIdentification, as: RBI} I don’t understand what that’s trying to specify. In this case, one is able to guess, though. For me personally, I enforce the Credo.Check.Readability.AliasAs and Credo.Check.Readability.MultiAlias Credo c…

[image] bmitc: personally feel that alias ___, as: ___ should be used extremely sparingly if not removed Using rarely, yes. Removing? No! We have a codebase with more than 600 modules at work. There are several modules ending in Product, within Schema, Dataloader, and what not prefixes. We …

Removed was a bit of a hyperbole. :stuck_out_tongue_closed_eyes: I know it won’t and probably shouldn’t happen in Elixir. Although, certainly several other languages, such as F#, do not have that feature, and I personally don’t miss it there. I’m not aware of it being in Erlang. Is that correct? Fo…

[image] bmitc: For Elixir, I got a bad taste for it at my previous company, where its use was definitely a symptom of poorly named modules. So many modules had such extremely similar names that as: ___ was used to mitigate this in modules and in tests. The moral of the story is that people will …

Erlang doesn’t have module aliasing at all. I’d say the biggest reason why as: is bad because if you wanted to do a global search and replace during refactoring, it makes it much more difficult. Same with alias Module.{…} I use neither in my codebases.

Ya, I’m not a huge fan of {} (though it has its uses though wouldn’t miss them if they were gone) and never use :as. I even avoid just plain old alias a lot of the time unless it provides significant noise-reduction. One of the big things that drew me to Elixir was the high level of locality that …

Yes, there is! Behold the dark art of context magic in Elixir alias (alias Guard.Rbac, as: RBI).{Cache, RoleBindingIdentification} Please do not try this at home

If I understand correctly, in your example RBI.Cache would ‘expand’ to Guard.Rbac.Cache, and same go for RBI.RoleBindingIdentification which would expand to Guard.Rbac.RoleBindingIdentification, right?

Multiple aliases in one line with as:

Questions & Help Questions

eksperimental July 24, 2022, 2:06pm 7

And how do you deal with external librarie modules?