Streamline live resource generation by inspecting the resource Ecto schema #696
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introspect the ecto schema and automatically inflect the schema name to infer the singular name, plural name and the pubsub event name. The following exmaple is copied from the
@moduledoc
. This makes it very succint to use Backpex to add an admin layer to a number of Ecto schemas with very little code.To use this functionality in your app, first define a new module in your application which encapsulates data that is common to all resources (repo, pubsub and layouts)
Now, you can define a new live resource using the module above
There are currently no integration tests for this (but then again, there are no integration tests for the rest of Backpex).