Any news on this one?

Any update on this?

Sorry to bump this but we're also in the same situation

Now that source maps in production by default seems to be the official Rails position, can we expect some movement on this?

If the bug is still there I think that it is better if it is open so others can find it if they run into the same issue.

Reopening #162

Now that v4 is released, maybe we can look again into merging this?

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

rafaelfranca closed this on Feb 27, 2018

We are still open to the idea but the implementation should leverage the attributes API introduced in Rails 5.2 in Active Model.

Is there are any possibility to speedup this pull-request to be merged?

Did you by any chance ever finish/publish your solution for this?

I close the issue but we can continue the discussion.

Any progress on this issue?

Sean, do you think someone can take a look at this? It's biting a lot of people and makes .or pretty much useless if you want the .or query to use a simple join, which is a pretty common use case. There are 57 likes in this issue alone.

I was wondering what is the status of this issue? The PR that fixes the problem is rejected but this issue is still open, so is it going to be fixed or is it intended behaviour?

Now that we triage by severity, setting this bug's priority to P2 to represent near-term backlog status.

By the nature of their profession, economists are often asked to expound on the appropriate role of government. In my opinion The Hand Behind the Invisible Hand provides us with a platform to discuss one of the most pressing issues of our time, namely the appropriate role of government.

Snap gets rid of dependency mess. Good. Snap offers in one place FOSS and proprietary app’s. Here I am suspicious. It may be an advantage for a commercial app-store and for some users. But this advantage may lead to loss of comfort and flexibility for the many users that rely first on FOSS.

snaps have many benefits that are huge: automatic updates List item shorter delivery times between develper and user possibility to use tracks and choose how much on the bleeding edge you want to be way more security and privacy, less dependency issues software available on the same versions independently of distributions and versions of distributions

I think this issue can be closed and new issues be created / referenced here for any related functionality that isn't in yet.

It is very important that "production ready" UI libraries are available because otherwise the use of Svelte cannot be argued. A key point would be to make it easy possible that people can contribute

If you continue to have trouble though, feel free to open a new issue so we can keep this one focused on the theme color palette documentation problem. 1 Pick your reaction

The imports in the published package should now be fixed in 3.29.5.

This seems to be #31189 . It should be fixed when you update to v17.03.0-ce

If the document is uncontroversial and agreement is reached quickly it might be committed directly with the "accepted" status. Likewise, if the proposal is rejected the status shall be "rejected". When a document is rejected a member of the core team should append a section describing the reasons for rejection.

Duplicate of #12079, please move all correspondence there!

We already are reserving a prop called slot so that we can do <Foo slot='bar'/> someday

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Fantastic reporting

I'm not sure I understand the problem, everything you are describing is already possible.

andrewdeandrade commented on Jul 31, 2015

instead of closing immediately, could we discuss some syntaxes that might work? I'm hardly an expert, so I'm not sure I can propose a syntax, but I can try to get the ball rolling:

We have cast universities as the arbiters of opportunity. We have assigned them the role of allocating credentials and defining the merit that the wider society rewards — economically, but also in terms of honor, recognition, and prestige. ADVERTISEMENT Being cast in this role has enlarged the economic and cultural importance of universities. But we’ve paid a price for it. For one thing, support for higher education has become a partisan matter.

Apologies for being "that person", but are there any updates on this topic or guidance in the meantime?

Personally for me, this is incredibly hard to read. Regex everywhere, nested objects with different rules and configurations that are very intuitive, multiple loaders that resolve backwards, built in loaders having obscure issues that require using third party loaders in between, separation of plugins and loaders, and so on.

GitHub issues aren't the right place for support questions like this. Please ask on StackOverflow or in our Discord chat room.

Ha, Mr. Betteredge, the day is not far off when the poor will rise against the rich.

GitHub Issues are preferred for discussion of this specification.

Nobody said we can't do this, I am arguing we should not do this.

Please don't put "feature request" items into GitHub Issues. If there's a new feature that you want to see added to Ruby on Rails, you'll need to write the code yourself - or convince someone else to partner with you to write the code. Later in this guide, you'll find detailed instructions for proposing a patch to Ruby on Rails. If you enter a wish list item in GitHub Issues with no code, you can expect it to be marked "invalid" as soon as it's reviewed.

given the popularity and the fact that I'm not convinced we shouldn't have first-class support for this

Even given all that, I haven't decided to close the door on offering this support in the future. If it was my opinion that we were not going to accept this ever, I would have closed the issue.

Priority labels

Severity labels

Type labels are very important. They define what kind of issue this is. Every issue should have one and only one.

Labeling is a task for everyone.

Categorizing Issues

There is a forum for discussing CommonMark; you should use it instead of github issues for questions and possibly open-ended discussions. Use the github issue tracker only for simple, clear, actionable issues.

If none of this worked, please comment in this issue and we’ll try to help. Try to create a small reproducing example — you might discover the problem as you’re doing it.

this is not intended to become a big, public thing. You're welcome to use anything and steal any code. Please do not count on us adressing feature requests or issues though.

Please submit questions like this on StackOverflow next time. People answers on GitHub don't compound as much