Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a unique "sytem name" to Demux::App #27

Open
rreinhardt9 opened this issue Dec 15, 2020 · 0 comments
Open

Add a unique "sytem name" to Demux::App #27

rreinhardt9 opened this issue Dec 15, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@rreinhardt9
Copy link
Contributor

Sometimes in the parent app, it's important to know something about one of the specific apps.

For example, if you want to show or hide some part of the UI depending on if a specific app has been connected.

Maybe you want to include a banner in an email encouraging them to try a new app but only if they haven't connected it yet.

Another example is if your parent app runs in multiple environments, your Demux::App records for the same "app" might all have different primary keys. If you want to run a data migration that impacts "app X" in all environments, it would be helpful to have a handle to refer to it that you could make the same in each of the environments.

In these cases, it seems like it would help to have a unique and stable way to refer to that specific app besides the primary key.

What if we add a column to Demux::App (maybe called system_name?) that would contain a string uniquely identifying this app ("slack_integration" for example).

It wouldn't really serve any purpose in the Demux library itself; which gives me some pause when adding it. But it would allow the parent app to interface with Demux in more meaningful ways...

@rreinhardt9 rreinhardt9 added the enhancement New feature or request label Dec 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant