#False positive with eslint-plugin-astro
1 messages · Page 1 of 1 (latest)
Not sure what you mean by make use of the rule
Just try targeting h2 h3 and h4 then
It's scoped so should only effect this componenents headings
Doesn't matter what type of component it is
Your targeting the underlying tag for styling
I'd argue that's a fundamental issue with how the plugin functions then as it has no way of knowing whether that class attribute is actually going to be used as a HTML class
Well that plugin is not an official Astro plugin to my knowledge
I wonder if extending the default attributes from headings into your prop type would help
Yes your fine posting here for support related to anything Astro even non official plugins
https://github.com/ota-meshi/eslint-plugin-astro/issues
So you cant open an issue here?
Can you send a full screenshot of the page? Seems more like a github issue?
I asked the author for how to configure the parser from this plugin in the past because I was trying to write my own config to fix issues I was having and seemingly got banned for it
What?
oh I see const Heading = Astro.props.headingEl || ("h2" as const);
m8 I can't read through every single code block in detail, sorry
Let's focus on the issue at hand and check the attitude at the door please
We are not staff, we are community members providing support in our free time
Please try to be a bit more respectful of that
That's not a staff roll, it's clearly explained in the roles info
it's both unhelpful and rude to barge into a thread
This is literally how volunteer support forums work. Please treat everyone here with respect, as the only reason they are in this thread is because they are interested in helping you. As previously stated, they have no other reason to be in here as they are not paid, nor in any other way receiving any benefit other than trying to bring new perspectives when people are stuck.
I was asked to post this bug report here as posting issues on github is not currently possible.
I hope people here are able to help you, but pointing out that we may not be able to solve issues with other repos here. Everyone is trying their best, and is welcome to leave this thread when it's no longer rewarding to them.
Question
@covert vortex If you apply the is:global directive, and add another just randomly named class that is not being used into your style tag, do you get the appropriate "no unused classes warning"?
Ah welp, if I think of any more ideas I'll get back to you here
Ah yeah I understand that now, I was confused
Well that's not something I can help you with unfortunately
Then, may I ask what you are doing with this thread? That feels unrelated here.
Several people have spent a lot of time trying to help, and you appear not to want that.
This is not the place for reporting bugs on other repos.
I can tell you how to get your issue reported though:
- Lose the attitude
- Have a bit more respect for the people you are dealing with online
- Reach out to the library author and attempt to make amends for your past behavior
Best of luck!
That's something you need to figure out on your own, I'm not hear to hold your hand on the path to being a better person
Right and that is great, but it's how you respond my friend
Things like 'im not a maintainer' or 'so you're wasting my time...'
These types of comments are unnecessary and only cause friction that ultimatley makes everyones lives more difficult
Since it's clear you don't want help, and this is not a place to report bugs on other repos, I think it's time to close this thread. I don't see any reason for it to remain open.
I don't need ideas, I need this bug reported,
Did I misunderstand this?
You want help reporting an issue on a repo you have been banned from, thus "side stepping" the repository owners wishes
I doubt anyone here would be comfortable doing that for you
If it's not a bug with us, there is nothing we can do about it.
Don't burn bridges 😛
Anyway, have a good one, hope you get things figured out!
Which is not a repo we control.
The difference is that they are different. You can check the github accounts. We also have a very established tradition of using the word "community" to differentiate from "official."
I hope that clears it up!
Official discord for the community
On the repo of the package you are having issues with (which is not maintained by astro)
No as it's not an astro issue
This repo that Hunter linked previously
You have already been told where the appropriate place for your issue is. We cannot help you with a repo outside of the withastro organization. I'm sorry that you're encountering an issue, but all we can do is provide (volunteer) support at this point, which you've already stated you're not interested in.
I'm going to suggest everyone leave this thread as it's clear that this is no longer a support issue.