2022-03-07 weekly planning

[kgodey]

About

At the start of each week, we start a discussion covering Mathesar's progress, team member check ins, and general updates. Everyone is welcome to add a new topic to discuss or to comment on existing topics.

Discussion topics

• Last Week in Mathesar
• Frontend priorities
• Backend priorities
• Design priorities
• Product priorities
• Comms Assignee schedule
• Sean's check in
• Ghislaine's check in
• Dominykas' check in
• Pavish's check in
• Kriti's check in
• Mukesh's check in
• Brent's check in

Weekly check-in

@centerofci/mathesar-core please post your weekly check-in as a top-level response and edit the discussion topics above to add your check in as a topic. Others are also welcome to respond.

Prompts:

• How did your most recent work go?
• What are you planning to work on soon?
• Do you anticipate any dependencies or blockers that someone else on the team can help you with?

If you'd like to add anything else to your check-in that's not related to the prompts, feel free to do so.

[kgodey]

Last Week in Mathesar

Feedback Requested

• Views Product Spec #1015
• Design for List Data Type – Viewing & Editing List #1034
• Design for List Data Type – Setting up & Filtering List #1136

Complete

• Milestones:
  • Working with Tables with 43 issues complete
• Discussions:
  • For the alpha release, how should we allow the user to enter newlines within cells? #1119
• Specs:
  • Update number type to support custom currency format mathesar-wiki#36
• Wiki updates:
  • The Product Spec for Views is done and is being reviewed, see the "Feedback Requested" section.
• Full stack and general work:
  • Upgrade Playwright to 0.2.3 #1139
  • Remove automatic review request workflow #1117
• Backend work:
  • Implement filtering options for Boolean types #388
  • Implement filtering options for Text types. #406
  • Implement filtering options for the email type #410
  • Implement filtering options for the URI type #413
  • Implement filtering options for the money type #418
  • Implement filtering options for date & time types #427
  • Implement filtering options for duration type #431
  • Column selecting operations should use attnum #992
  • Column dropping operation should use attnum #993
  • Column creation and copying should use attnum #995
  • Implement filter name aliases for specific parameters #1092
• Frontend work:
  • Frontend implementation for Text Mathesar type #254
  • Frontend work for working with columns #327
  • Implement setting a column as non-nullable or unique #499
  • Wait until user is done editing a cell before saving #928
  • Eliminate TypeScript types like undefined | null #1113
  • Refactor front end Meta class and a lot of surrounding code. #1109

[kgodey]

Frontend priorities

1. Complete front end changes to Mathesar 896 Change records api parameters to use column id instead of name #1047
   1. PR: UI changes for column ids in records API #1141
2. Get open PRs merged:
   1. Menu components #1076
   2. Add code comments linking to discussions #1133
3. Make progress on issues to lay groundwork for Initial Data Types milestone:
   1. NumberInput component improvements #970
   2. Add context menu to set cell value to NULL #930
   3. Decide on date/time formatting string syntax #1108
   4. Improve UX for configuring Text type DB settings #1118
   5. Frontend implementation for Boolean Mathesar type #257
4. Continue working on other Initial Data Types frontend issues.

@pavish @seancolsen Please comment below with thoughts/concerns.

[seancolsen]

Looks good.

#970, #930, and #1108 are all tickets I've been planning to work on. I'm planning to raise some questions about #970 before I begin work, and I'm hoping that #930 and #1108 will both be fairly quick. So I'll add a few more tickets to the list, as possible tickets I'd work on this week, if I'm out of un-blocked work with the above list:

• Filter/Sort/Group are broken when referencing a deleted column #987
• Records fail to load after renaming a table twice #982
• Refactor Select and SimpleSelect components, merging them into one #1099

[seancolsen]

Now that @pavish has clarified that #775 is in fact not blocked, I'll be adding that near the top of my list. My list is:

• NumberInput component improvements #970 (though I need to have some clarifying conversations before starting work)
• Improve UX when adding new records to a table with a NOT NULL column #775
• Add context menu to set cell value to NULL #930
• Decide on date/time formatting string syntax #1108
• Filter/Sort/Group are broken when referencing a deleted column #987

Not saying I'll get all that done this week though. We'll see how far I get.

[pavish]

Looks good to me.

[kgodey]

Backend priorities

The frontend is catching up fast to the backend, so we really need to get backend work for completed and start on Links between Tables ASAP.

Remaining issues:

1. Get open PRs merged:
   1. Mathesar 896 Change records api parameters to use column id instead of name #1047
   2. Split datetime into three UI types #1093
   3. Replace column index usage in db column alter operations with column attnum. #1132
   4. Add non-composite custom money #1137
2. Complete remaining backend work for Initial Data Types:
   1. @dmos62:
      1. Suggest popular/standard URI schemes as values for appropriate filter parameters #1097
      2. Resolve logic duplication in the db.types namespace #1100
      3. Inconsistent database type name casing in backend code #1036
      4. Add database type alias information to database type endpoint #1037
   2. @mathemancer
      1. Spec for human readable date and time parsing #845
      2. Grouping:
         1. Implement grouping for Text types. #408
         2. Implement grouping options for the email type #411
         3. Implement grouping options for the URI type #414
         4. Implement range based grouping for numeric types. #384
         5. Implement grouping options for date & time types #429
         6. Implement grouping options for money types #419
         7. Implement grouping options for duration type #432
   3. @silentninja:
      1. Replace column index usage with attnums and Column model id #839
         1. Column alteration operations should use attnum #994
      2. Remove column_index from MathesarColumn class #996
      3. Ensure that we can set, get, and delete default values for all types #1064
      4. Implement display options for the custom Money type #1105
   4. Unassigned
      1. The type inference algorithm should use TEXT rather than VARCHAR #1121
3. Start work on backend work for Links between Tables, some ideas:
   1. Modify constraints API to list foreign key constraints #943
   2. API support for storing "record preview" and "record selector" settings #944
   3. Ensure integrity of columns with foreign key constraints applied #973
   4. API support for "Link Table" dialog #972
4. I should have time to start on Set up style guide and tooling for consistency in backend code #1008 this week.

@dmos62 @mathemancer @silentninja Please comment below with thoughts/concerns.

[dmos62]

Sounds good. My tasks are pretty clear cut. URI scheme suggestions are still slightly fuzzy, but I'll figure it out.

[mathemancer]

The priorities make sense. I think there are dependencies between us for most current issues, but we'll work through it.

[kgodey]

Design priorities

1. Complete wireframing and draft a spec for Design for visual query builder ("Data Explorer") #1065
2. Design discussions for Design for List data type #978

@ghislaineguerin @ppii775 Please comment below with thoughts/concerns

[ghislaineguerin]

@kgodey This looks good. As discussed, the plan is to start writing specs for #1065 tomorrow. As for #978 we discussed updates to the issue regarding the examples and scenarios so that @ppii775 can incorporate them into the design.

[kgodey]

Sounds good @ghislaineguerin. I did add some examples to #978 in the comments so we should be good to go there.

[kgodey]

Product priorities

1. Finalize product spec for Views based on feedback from discussion.

[kgodey]

Comms Assignee schedule

Week	Person
2022-03-07 to 2022-03-11	Kriti
2022-03-14 to 2022-03-18	Pavish
2022-03-21 to 2022-03-25	Mukesh
2022-03-28 to 2022-04-01	Sean
2022-04-04 to 2022-04-08	Dominykas
2022-04-11 to 2022-04-15	Ghislaine
2022-04-18 to 2022-04-22	Brent

Instructions

You can also find the schedule and instructions for the Comms Assignee on the wiki page. Please feel free to update the wiki page if you think of anything useful during your shift.

[seancolsen]

Sean's check in

How did your most recent work go?

• Last week went well. I'm happy about my progress.

What are you planning to work on soon?

• See 2022-03-07 weekly planning #1142 (reply in thread)

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

• Nope

[ghislaineguerin]

How did your most recent work go?

It went well. Product discussions were helpful.

What are you planning to work on soon?

See #1142 (reply in thread)

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

• Not for now.

[dmos62]

How did your most recent work go?

Jumped into coding solutions for the URI scheme recommendation issue too early. Ended up repeatedly discarding work, because didn't explore the issue beforehand enough.

What are you planning to work on soon?

The task list in the backend priorities post is accurate. I'll start the week with the URI scheme recommendations. I've also a PR review lined up.

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

No.

[pavish]

Pavish's check in

How did your most recent work go?

Pretty well. Most groundwork for type implementation on the frontend is complete.

What are you planning to work on soon?

• A draft PR for text type updates is raised: Text type updates #1144. I'm planning to get it ready first.
• Then I'd work on Frontend implementation for Boolean Mathesar type #257, which includes groundwork for display options for all types. Once that is ready, we can work in parallel on types on the frontend.
• If I get time, I'll start working on implementing another type. I'll decide which ones when I'm ready to begin.

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

None

[kgodey]

Kriti's check in

How did your most recent work go?

Good, the Views spec is mostly done. It took much longer than I thought it would and I'm glad to be moving on to other work. I do think it's going to be great when implemented.

What are you planning to work on soon?

• Updating the Views spec to its final form based on feedback from Views Product Spec #1015
• Updating design tickets for the Views milestone to match the product spec.
• Starting work on Set up style guide and tooling for consistency in backend code #1008
• Comms around Google Summer of Code

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

If anyone has feedback about the Views spec, please comment on #1015 in the next day or so. I'm considering the spec closed after that.

[silentninja]

Mukesh's check in

How did your most recent work go?

It went well. Got most of the column index replacement PRs merged.

What are you planning to work on soon?

Will be working as per the backend priorities list.

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

I have started a discussion to finalize on the identifier for DML operations. It is preventing the backend work on #1047

[mathemancer]

How did your most recent work go?

It went well, though the custom money type was more work than I originally thought.

What are you planning to work on soon?

I'm finishing up the date/time spec, getting my money type PR merged, then getting into grouping. Alongside that, I (we) will be managing an influx of GSoC-related contributors, hopefully.

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

Grouping has a dependency on the column ID work @silentninja is doing, along with the resolution to some discussions.