-
Notifications
You must be signed in to change notification settings - Fork 8
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
CS-7790 CS-7791 New CRM task tab and planner #2042
Conversation
index?: number; | ||
} | ||
|
||
export class CRMTaskPlannerIsolated extends Component<typeof CRMTaskPlanner> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was hoping there was more re-use of a component here. Can we extract a component from the isolated work tracker first.
If I had a list of todos and days of the week, cud I make a work tracker from that using the same template
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tintinthong indeed it's a good time to extract and reuse the base task planner component before it grows up on other use cases.
In this new base task planner component, we are able to pass dynamic columns config from the consumer level. Hence its doable on your scenario to map columns by days of the week inside the config
You may see some examples within the sprint planner and crm task planner in this PR, thanks
columns: TaskColumn[]; | ||
} | ||
|
||
export class BaseTaskPlannerIsolated< |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it more straightforward to get this to be a GlimmerComponent that is used inside the isolated template?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tintinthong I was trying GlimmerComponent with straightforward type declaration like this
export class BaseTaskPlannerIsolated extends GlimmerComponent<BaseTaskPlannerIsolatedSignature> {
It turns out there is a bunch of lint errors because the base task planner is not extending to the type to SprintPlanner/TaskPlanner
https://github.com/cardstack/boxel/actions/runs/12823222126/job/35757386460?pr=2042
If I use something like this with GlimmerComponent it works now, but not sure is more straightforward
export class BaseTaskPlannerIsolated<
T extends typeof CardDef = typeof CardDef,
> extends GlimmerComponent<
BaseTaskPlannerIsolatedSignature & { Args: { model: InstanceType<T> } }
> {
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reverted to original approach
23acc8b
to
71bb5ba
Compare
This reverts commit 71bb5ba.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. File a ticket for better refactoring of the task planner component
Ticket for refactoring: https://linear.app/cardstack/issue/CS-7888/refactor-task-planner-component |
Refer to
What is changing
Task
tab in CRM appCRM Task Planner
CRM Task
Task
Contact
with Representative as assignee because our representative (staff) save as contact right nowAccount
Deal
Screenshot