sezaru
So, normally I like to restrict my alias scopes as little as possible, so instead of adding an alias in the top of a file, I prefer to do it inside a code block.
On older versions of Ash, adding the following code:
policies do
alias Marketplace.Markets.Checks, as: MarketsChecks
policy action([:place_offer]) do
forbid_if MarketsChecks.NotConfirmedYet
forbid_unless MarketsChecks.IsInvestor
authorize_if always()
end
end
Will work fine, but using the latest version, now it gives me the following warning during compilation:
warning: unused alias MarketsChecks
lib/marketplace/markets/offer.ex:80
Note that even with the warning, the policy above still works fine.
Is it a easy fix to make this warning go away? I do the same in other code blocks (relationships, calculations, attributes, etc) and they all work fine, I’m only seeing this on the policies block
Where Next?
Trending in Questions
Other Trending Topics
Latest Ash Threads
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 10 of 10 Posts
zachdaniel
sezaru
No, got the same warning putting it at the top
zachdaniel
Let’s double check your spark version. Do
mix deps.update sparkand see if that helpssezaru
I’m already in the latest version (1.1.48)
zachdaniel
Hmm…oh, could you perhaps try and remove the
asoption to the alias and see if the warning goes away?sezaru
Removing the
asoption fixed it. But, if possible, I would like to keep it since I added that because it conflicts with another alias that has the same nameCheckszachdaniel
Yeah, that makes sense. We made a special thing to avoid these issues, and I suspect it isn’t properly handling
. Can you open an issue in
asaliasesspark? In the meantime, you can use the alias you want but add, warn: falseoption.sezaru
Was that a recent change? Because, weirdly enough, not so old version worked just fine
I will create a ticket in spark ASAP
zachdaniel
I don’t think it was a recent change but its possible…
sezaru
https://github.com/ash-project/spark/issues/64