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

General Updates

• We're very close to closing the Working with Tables milestone, we only have one issue left!
• We've merged in a few major projects, including:
  • API error handling standardization
  • Type configuration on the frontend

Feedback Requested

• Discussions in progress:
  • Shipping more quickly #1046
  • Dynamic Type selection & customization on the frontend #1035
  • Design for List Data Type – Viewing & Editing List #1034
  • Code Styling guidelines for the backend #1007
• Specs in review:
  • None at the moment
• PRs needing review:
  • Please see frontend and backend priorities sections.

Complete

• Major wiki updates:
  • We've been working on Google Summer of Code project ideas
  • The Formulas page has been added to the Views product spec.
  • Front end coding standards update: Add three new front-end coding standards mathesar-wiki#33
• PRs merged:
  • Full stack:
    • Modify constraints API to use column id instead of column name #1026
  • Backend:
    • Handle error consistently on the backend using custom drf error handler #1016
    • Fixes #859 Return proper error response on not null violation #1017
    • Convert API layer error responses into Errors that conform to the API spec #991
  • Frontend
    • Type configuration for Text, Number, Boolean, and all mathesar types with single associated db type #926
    • In-app help content #1024
    • Keyboard Accessibility Pagination Component #963
    • UI for adding multi-column unique constraints #1005
    • Implement renaming a column #976
    • Display null while editing a null cell #961

[kgodey]

Frontend priorities

1. Get Google Summer of Code ideas written up, this is top priority because of an external deadline.
2. Frontend work for Introduce ui and db API namespaces #1041
3. Review and merge PRs ready for review.
   1. Fix spelling error in function name #1048
4. Complete Improve UX when adding new records to a table with a NOT NULL column #775
5. Complete and merge basic E2E testing: Write integration tests for some important user scenarios #640
   1. PR: Improve E2E test setup #1032
6. Make progress on issues from the Initial Data Types and 2022-02 improvements milestones. Some ideas:
   1. Implement setting a default value for a column #500
   2. Create Menu component #742
   3. NumberInput component improvements #970
   4. Wait until user is done editing a cell before saving #928
   5. Blur via keyboard after entering edit mode on a NULL cell should cancel edits #929
   6. Add keyboard shortcuts for setting a cell to NULL #936

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

[seancolsen]

Looks good.

I'll be prioritizing #775 and then #640. I expect those to take most/all of this week, especially since it's a 4-day week for me.

I don't have any GSoC project ideas, so I don't plan to spend any time with that.

I'm happy to do the front end work for #1041, but I'd like to give @pavish a chance to volunteer if he likes since I jumped on #862 and #1026 pretty quickly.

I plan to do the font end work on #1047 once it's ready.

Also, #619 is now pretty high on my priority list since @pavish and I have agreed on a simpler path towards closing that one, so I'd be keen to pick that up after resolving all of the stuff I mentioned above.

[pavish]

Sounds good to me.

@seancolsen I'll take up the frontend work for #1041

[kgodey]

Backend priorities

The frontend is catching up fast to the backend, so we really need to get backend work for Initial Data Types completed and start on Links between Tables ASAP. We won't be able to do that this week, but the closer we get, the better.

1. Get Google Summer of Code ideas written up, this is top priority because of an external deadline.
2. Filtering:
   1. Get the following PRs merged:
      1. Introduce function API #1022
      2. Introduce ui and db API namespaces #1041
   2. Create PR for new filters API and get that as close to merge as possible.
   3. Start working on individual data type filtering issues:
      1. Implement filtering options for Number types. #385
      2. Implement filtering options for Text types. #406
      3. Implement filtering options for the email type #410
      4. Implement filtering options for the URI type #413
      5. Implement filtering options for date & time types #427
3. Basic Data Type Support:
   1. Handle INTERVAL type in the backend #430
   2. Handle MONEY data type in the backend. #420
   3. Backend work for Mathesar money custom type  #417
4. Replace column name usage with ID:
   1. Replace column index usage with attnums and Column model id #839
      1. Column selecting operations should use attnum #992
      2. Column dropping operation should use attnum #993
      3. Column alteration operations should use attnum #994
      4. Column creation and copying should use attnum #995
   2. Modify records API to use column id instead of column name #896
5. Date and time spec: Spec for human readable date and time parsing #845
6. Data Type API updates:
   1. Split Date & Time data type into three Mathesar types  #960
   2. Inconsistent database type name casing in backend code #1036
   3. Add database type alias information to database type endpoint #1037
7. 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
8. Default values: Translate server_default values #648

That still leaves the following blocked issues, which we can get to once the all the issues under (3) are done:

1. Implement filtering options for duration type #431
2. Implement grouping options for duration type #432
3. Implement display options for Duration type #433
4. Implement filtering options for the money type #418
5. Implement grouping options for money types #419

I didn't put #1008 in here but I'll be working on it if I have time this week.

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

[silentninja]

I can work on issue #420 and then move on to text grouping issues.

[kgodey]

Design priorities

1. Get Google Summer of Code ideas written up, this is top priority because of an external deadline.
2. Design specs for:
   1. Query builder - ticket will be created soon.
   2. Support for opening and interacting with a View #466
   3. Design for List data type #978
   4. Improve support for finding duplicate rows #1028
3. Continue exploratory work for Views in the design prototype.

@ghislaineguerin @ppii775 Please comment below with thoughts/concerns

[kgodey]

Product priorities

1. Get Google Summer of Code ideas written up, this is top priority because of an external deadline.
2. Update Views design issues with requirements based on the new product spec for Views and further exploration.

[kgodey]

Comms Assignee schedule

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

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.

[dmos62]

How did your most recent work go?

Nothing to report about my tasks.

I'm happy about the meta discussions around the feature-oriented v. architecture-oriented work. There's a sense of growth in the air.

What are you planning to work on soon?

Get the function API and API namespace PRs merged. Make as much progress on filtering API as possible.

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

No.

[seancolsen]

Sean's check in

How did your most recent work go?

• Going well. I'm happy that we're all working on picking up the pace a bit.

What are you planning to work on soon?

• See my comment in "Frontend Priorities".

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

• Nope

[pavish]

Pavish's check in

How did your most recent work go?

It went pretty good. Nothing major to report in particular.

What are you planning to work on soon?

I'm planning to get the following done this week:

• Split frontend issues for initial data types into
  • Type switching with database options (includes sending type_config)
  • Implement display options
  • CellInput for the type
  • Filters (Common issue for all types)
  • Groups (Common issue for all types)
• Work on newly created issues for Boolean, Text and Number
• Number component improvements

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

None

[kgodey]

@pavish Will CellInput also cover styling issues (e.g. fixed width font for numbers?)

[pavish]

I initially planned to create a single PR for the CellInput component. I realized it would be better to handle it type by type. The first PR for Boolean might take a little longer than the rest, since it may include additional ground work.

[pavish]

@kgodey It will cover everything mentioned in the parent issue description. For Number, monospace font is included in the issue description, so we will cover it.

It will introduce styling inconsistencies though, so any additional styling fixes can be taken up in the UI styling milestone, or as subsequent issues.

[kgodey]

Sounds good, thanks @pavish.

[mathemancer]

Brent's check in

How did your most recent work go?

Pretty slowly, since I was out for lunar New Year most of last week. That said, I'm glad we synced a bit on how to increase velocity. I'm still working on the interval type; it's taking longer than I thought, mostly due to trying to interpret some of the more esoteric sections of SQLAlchemy docs.

What are you planning to work on soon?

I have the interval type working, I'm hooking it up to the API and testing. After that, I'm on the grouping tasks.

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

@dmos62 I'll hit you up this week to try to hook up a grouping function to the new functions API and hints framework. I think if we can get that to work without too much fuss it'll save duplicated work.

[kgodey]

@mathemancer I think it would make sense to prioritize the Money types over grouping tasks - those are the last "data type support" issues to complete and will unblock all remaining grouping, filtering, and display options tasks.

[mathemancer]

Sure, I could do that.

[kgodey]

Actually, it seems like @silentninja is working on money types, so never mind.

[kgodey]

How did your most recent work go?

It went well, I think @ghislaineguerin and I are finally figuring out a coherent version of how Views will fit together, there's fewer unknowns and I think most of them are known unknowns. The tickets and spec are out of date / half-finished / all over the place at the moment, I hope that by the end of the week, they will be more coherent.

I'm also glad we talked about increasing velocity, I'm looking forward to seeing us move faster.

What are you planning to work on soon?

• Google Summer of Code ideas and coordination
• Hopefully finalizing Views product work and design tickets
• Set up style guide and tooling for consistency in backend code #1008

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

We all need to finish work on Google Summer of Code ideas soon, but that should be covered under individual priorities.

[ghislaineguerin]

Ghislaine's Check-in

How did your most recent work go?

Having more collaboration w product (@kgodey ) is helping to move forward and unblock design work related to views. I think it went well in terms of focus, and the scope is a lot more manageable than in previous weeks.

What are you planning to work on soon?

Continue exploratory work for Views in the design prototype.

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

None

[silentninja]

Mukesh's Check-in

How did your most recent work go?

It went well, finally got the error handling PR's merged and the integration test setup is going along quite well.

What are you planning to work on soon?

Looking to work on the Money type issue and text grouping issues.

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

None