• I'm submitting a ...

  • Bug report
  • Feature request
  • Translation

• Do you want to request a feature or report a bug?

  • Feature

• What is the current behavior?
  Doesn't have this feature as far as i know.

• What is the expected behavior?
  I request a function of the Ralim firmware that enables either at start-up or through a menu opti

FYI
Readme says:

def deps do
  [{:coherence, "~> 0.6"}]
end

However, in https://hex.pm/packages/coherence it only has version 0.5.2. Users get this error:

➜  path-to-project git:(master) ✗ mix deps.get
** (Mix) No matching version for coherence ~> 0.6 (from: mix.exs) in registry

The latest version is: 0.5.2

See screenshot. Thank you!

![screen s

For checkbox inputs of associations with unique pluralization requirements, e.g. specialty/specialties, ExAdmin incorrectly pluralizes the <association>_ids param key: specialtys.

In https://github.com/smpallen99/ex_admin/blob/master/lib/ex_admin/param_associations.ex#L34, if you replace

new_key =
  String.replace_suffix(key_as_string, "_ids", "s")
  |> String.to_atom()

It'd be very useful to be able to edit these colors once defined here. Also, perhaps adding rgba as an option would be handy, as opacity can be defined in the picker.

The docs specify the following attributes for creating a Stripe.Invoice

https://github.com/code-corps/stripity_stripe/blob/caa2d8dda5673e84fc5540856e9fae6b987dfe84/lib/stripe/subscriptions/invoice.ex#L182-L198

It is still possible to pass in a collection_method as specified in the Stripe API but it would be nice to have it detailed here.

Opening for comment.

Geth recently became more strict and now rejects many hex values that have leading zeroes (ie 0x02 instead of 0x2).

The official RPC spec dictates that quantities should have no leading zero, and unformatted data should.

For this reason, it

Firebase now supports an analytics label in FCM, which can be really useful in combination with Big Query and such.

This is only supported in the current API as far as I can see, so supporting this would probably require moving to that one, making this a little more complicated.

https://firebase.google.com/docs/cloud-messaging/understand-delivery#adding_analytics_labels_to_messages
https://

If this had been included in the examples, #85 would not have occurred.

Hello!

Would be nice and useful, if wxHE has a separate window for displaying file-structure of MZ-PE, ELF and Mach-O formats. Doable?

[1] http://www.skyfree.org/linux/references/ELF_Format.pdf
[2] https://source.winehq.org/source/include/winnt.h
[3] https://www.microsoft.com/en-us/download/confirmation.aspx?id=19509
[4] https://lowlevelbits.org/parsing-mach-o-files/

Hi all! First of all thank you for building this wonderful piece of API.

But I cannot seem to find the documentation similar to this:
https://www.twilio.com/docs/sms/tutorials/how-to-receive-and-reply-java

I'm trying to receive SMS messages in Twilio from users.

The README contains REPLACE_OS_VARS in Distillery, but it links to a 404 Not Found page.

Maybe https://hexdocs.pm/distillery/config/runtime.html#option-2-vmargs could be the correct new link target?

I guess it would make most sense to co-locate the docs (in a docs/ folder) with the code, so that we can serve it from https://evercoder.github.io/culori via GitHub Pages. The downside is that docs/ would have its own package.json and associated apparatus, and will contain HTML templates along with the Markdown content files, but that might be fine.

We can use [eleventy](https://www.11ty.i

Generate documentation that looks somewhat better than the default edoc style (look at elixir docs).
Figure out how to publish (eg. maybe both Erlang API from xprof_core and REST API/GUI guide from xprof_gui should be copied/duplicated under xprof app documentation).
What should be the source format of non-edoc pages/guides (eg markdown)

The README states:

Type casting. Mnesia can store any data in any field, including strings, numbers, atoms, tuples, floats or even PID's. All types in your migrations will be silently ignored.

I just tried to migrate a Postgres-app over to Ecto_Mnesia, and it was unable to run my migrations because I had references("table_name") fields in there. Since this is also 'just a type', I think b