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

Notification Blueprint Generation #17

Open
SychO9 opened this issue Aug 18, 2021 · 2 comments
Open

Notification Blueprint Generation #17

SychO9 opened this issue Aug 18, 2021 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@SychO9
Copy link
Member

SychO9 commented Aug 18, 2021

No description provided.

@SychO9 SychO9 added the enhancement New feature or request label Aug 18, 2021
@SychO9 SychO9 added this to the 1.1.0 milestone Aug 18, 2021
@SychO9
Copy link
Member Author

SychO9 commented Aug 18, 2021

This is very interesting btw, this is a situation where I feel like the separation of backend/frontend doesn't help, if we're generating a new notification type/blueprint, it would be neat to do everything from backend class to frontend component.

@askvortsov1
Copy link
Sponsor Member

This is very interesting btw, this is a situation where I feel like the separation of backend/frontend doesn't help, if we're generating a new notification type/blueprint, it would be neat to do everything from backend class to frontend component.

Agreed: we should have steps for each, but one command that does backend + frontend + extender.

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

2 participants