2022-03-21 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
• Brent's check in
• Pavish's check in
• Ghislaine's check in
• Kriti's check in
• Mukesh's check in
• Dominykas' 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

• Enums, enumerations and database types #1184
• Conventions around schema used for test cases. #1193
• New engineering wiki structure #1192

Complete

• Discussions:
  • Relax the concepts of records and data transformations #1154
  • Explicit column ordering #1186
• Full stack and general work:
  • Add E2E test for trying to convert a text column of words to a number column #1129
  • Add E2E test for moving the selected cell with arrow keys #1130
  • Add E2E test for trying to to rename a table to the name of another table #1125
  • Add E2E test for renaming a table #1124
  • Add E2E test for deleting a table #1123
• Backend work:
  • URI type does not allow NULL value to be set. #1156
  • Ensure that we can set, get, and delete default values for all types #1064
  • Uppercase db types in db types endpoint #1176
• Frontend work:
  • [UI] Error message gets displayed even when the table name is set to its prior name #1161
  • Remove url prefixing on frontend #1054
  • Improve UX for configuring Text type DB settings #1118
  • Text overflow should be represented by ellipsis in schema selector #984
• Documentation work:
  • Spec for human readable date and time parsing #845

[kgodey]

Frontend priorities

1. Get open PRs merged:
   1. Number component #1155
   2. Added e2e test for converting a text column of numbers to number column fixes #1128 #1170
   3. Add E2E test for converting boolean type to text type #1182
   4. Switching a schema from the Manage Schema #1191
2. Make progress on high-priority issues 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. Frontend implementation for Boolean Mathesar type #257
   5. Improve UX when adding new records to a table with a NOT NULL column #775
3. Continue working on other Initial Data Types frontend issues.

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

[seancolsen]

Looks good

[pavish]

Looks good to me

[kgodey]

Backend priorities

1. Get open PRs completed and merged:
   1. Minor refactor recycled from closed PR #1174
   2. Avoid inferring type varchar #1188
   3. Add db type alias information to db types endpoint #1190
   4. Switching a schema from the Manage Schema #1191
2. Complete remaining backend work for Initial Data Types:
   1. @dmos62:
      1. Resolve logic duplication in the db.types namespace #1100
      2. Add database type alias information to database type endpoint #1037
   2. @mathemancer
      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
      2. Remove column_index from MathesarColumn class #996
      3. Implement display options for the custom Money type #1105
   4. Not assigned to core team members:
      1. API should validate input for number columns #1145 (assigned to @ManishShah120)
      2. Batch updating column using /tables/ api should reference column using id instead of column_index #1167 (unassigned)
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. Set up style guide and tooling for consistency in backend code #1008

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

[mathemancer]

I think this makes sense.

[dmos62]

Makes sense.

[kgodey]

Design priorities

1. Publish spec and start review process for Design for visual query builder ("Data Explorer") #1065
2. Continue iterating on Design for List data type #978

@ghislaineguerin @ppii775 Please comment below with thoughts/concerns

[ghislaineguerin]

Looks good to me. I will continue working on #1065

[kgodey]

Product priorities

No product work is planned for this week.

[kgodey]

Comms Assignee schedule

Week	Person
2022-03-21 to 2022-03-25	Mukesh
2022-03-28 to 2022-04-01	Sean
2022-04-04 to 2022-04-08	Ghislaine
2022-04-11 to 2022-04-12	Kriti
2022-04-13 to 2022-04-15	Dominykas
2022-04-18 to 2022-04-22	Brent
2022-04-25 to 2022-04-29	Kriti
2022-05-02 to 2022-05-06	Pavish

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?

• It's kind of crazy that my Number component is still in draft state. At this point I'm waiting for a sync call with Pavish where we can discuss the best approach to fixing a regression from my work that an E2E test uncovered. Aside from that (hopefully small) issue, the PR should be ready to bring out of draft state, which I'm very excited about. I never imagined that data entry of numbers could be so complex! But all-in-all I'm very happy with how this PR has turned out, even though it took a while.

• Since our involvement in GSoC began, I'm definitely spending significantly less time on my own code because I'm reviewing more PRs, helping more people, and following more discussions. All things considered, this seems good. But I'll have somewhat lower expectations for my own output during GSoC.

What are you planning to work on soon?

• Add context menu to set cell value to NULL #930
• Decide on date/time formatting string syntax #1108
• Improve UX when adding new records to a table with a NOT NULL column #775

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

• Need to chat with Pavish about NumberInput, but that's on his radar and we may even be able to do that today.

[mathemancer]

How did your most recent work go?

I had some family stuff come up that meant working while managing the baby. However, this gave me a good reason to jump into more PR reviews and documentation, which went well.

What are you planning to work on soon?

I really want to focus more on coding this week than last, specifically on grouping.

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

Not at the moment.

[pavish]

Pavish's check in

How did your most recent work go?

The PR for updates for text and groundwork for db type determination is merged. The groundwork for display options is mostly done with some race conditions to work out. I'm working on the boolean display options, which is taking slightly more time than anticipated.

I've also been focusing on helping new contributors the last week and it's been going well.

What are you planning to work on soon?

• Complete boolean type implementation
• Setup display options for number and money (This is different from the implementation of cells)
• Start work on data & time types implementation, if I get the time.

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

None

[ghislaineguerin]

How did your most recent work go?

It went well, lots of discussions around Data Explorer and specs.

What are you planning to work on soon?

#1065 Finalize Spec

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

None

[kgodey]

How did your most recent work go?

I haven't gotten much focused work done in the past week, there's a lot more day-to-day activity and discussion since the GSoC contribution period started. That's fine, though. I've also been spending a fair amount of time on the query builder design with @ghislaineguerin.

What are you planning to work on soon?

• Keep up with day to day stuff
• Continue and hopefully work on Set up style guide and tooling for consistency in backend code #1008
• Keep reviewing draft work on Design for visual query builder ("Data Explorer") #1065

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

No.

[silentninja]

How did your most recent work go?

Progress was really slow with the issue that I am currently working on(Money type display options). On the other hand, there was a good amount of discussion with GSOC contributors.

What are you planning to work on soon?

• Finish the remaining issues listed in the backend priorities section.
• Help contributors with the codebase and add documentations that would be helpful to new contributors

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

No.

[dmos62]

How did your most recent work go?

Ran into some technical debt and ended up taking a deep dive into type logic related stuff in Mathesar. That was productive in that I've gotten a better understanding of our backend, and there's a pretty nice refactor under-way, but at the same time I've contributed little code during last week.

What are you planning to work on soon?

• flesh out the mentioned refactor
• custom error debugging related issue
  • assign self or find someone else to take the task
  • Error handler should not capture exceptions in DEBUG mode #1151
• start working on next milestone.

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

No.

[kgodey]

@dmos62 Will the type refactor also resolve #1037 (by removing aliases from the API?)

[dmos62]

Yes, it will.

[kgodey]

Great, thanks!