Zachary Golba

> However I think we can also achieve this using babel's ignore and rollup's exclude. That's how this would be handled internally. The reason the `import` api would exist is...

Hey! Thank you for your interest in Lux. 😃 Currently the model layer of Lux only supports SQL databases. However, it is not impossible to use DynamoDB with Lux, you...

Hey, thank you for using Lux! Unfortunately, the way id's are resolved from route params only work for integers in the current version. This is an issue we're planning to...

@seawatts It's possible but may be an after `1.0` fix

@jamemackson The reason why this is occurring is because Lux is not prebuilt when it is published (by design). This is because the core Lux API is bundled with applications...

This is a great idea @kevboh!

@gentle-noah I appreciate the enthusiasm! Currently, we a working on a landing page/documentation website for Lux. I think we should hold off on this issue until we finish the landing...

@seawatts I thought you were able to deploy to eb successfully? What issue(s) are you having?

@nickschot you are not required to supply all not nullable attributes for custom actions. The constraints are only for built-in `create` and `update` methods. IMO, a more appropriate solution is...

I was referring to using the meta property for the request however, that would still require whitelisting via the `Controller#query` array. Let me think about this one for a bit....