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

Pull 66 add todo journal #84

Merged
merged 13 commits into from
Jan 8, 2024
Merged

Pull 66 add todo journal #84

merged 13 commits into from
Jan 8, 2024

Conversation

arran4
Copy link
Owner

@arran4 arran4 commented Jan 8, 2024

No description provided.

spslater and others added 8 commits April 3, 2023 03:36
- Add methods for VTodo and VJournal
- Changed the shared properties to be attached to the ComponentBase
  so those methods don't need to be repeated across all attributes
  that share them
- If a property is shared across some, but not all components, then
  it's a private method on the ComponentBase and public method on
  the Components (eg LOCATION for Event and Todo but not Journal)
- Shifted position of some Event methods in the file to live after
  the VEvent struct
- Add methods for Alarm, Timezone, and FreeBusy
- Only methods for creating and adding right now, will add methods
  for the properties unique to them later
- Recursive call for Alarms
- SetGeo was not a public method
- Missing comma in struct creation
… into pull-66-add-todo-journal

* origin/pull-66-add-todo-journal-orphan:
  Add changes for All Day Events to All Day Todos
  Add Comment and Category Properties to Components
  Fix Typos in a couple places
  Add Alarm, Timezone, and FreeBusy Property Methods
  Add Todo and Journal Property Methods

# Conflicts:
#	calendar.go
#	components.go
@arran4 arran4 self-assigned this Jan 8, 2024
@arran4
Copy link
Owner Author

arran4 commented Jan 8, 2024

Hi @spslater Sorry about the mistake on #66 when merging in current updates. I have attempted to fix it here. Can you please review to see if I introduced any issues?

@arran4
Copy link
Owner Author

arran4 commented Jan 8, 2024

image

Well that doesn't sound good.

@arran4
Copy link
Owner Author

arran4 commented Jan 8, 2024

Lint saved the day.. Gaps in testing by the looks of it.

@spslater
Copy link
Contributor

spslater commented Jan 8, 2024

I'm reading thru it now to make sure everything looks good and catch any new functions that wouldn't have been originally changed.

@arran4
Copy link
Owner Author

arran4 commented Jan 8, 2024

@spslater Thanks. There were a couple of relocations which made the merge a bit harder. If I had more time to work on this there is a lot I would like to improve.

@spslater
Copy link
Contributor

spslater commented Jan 8, 2024

For sure, I should've really split it into 3 pull requests to make reviewing it a lot easier. I'll go in and do the official review. Later I will open a new pull request for any newer functions / ones that I missed. It'll be easier to catch them and make those changes that way. But everything I originally changed looks good.

Copy link
Contributor

@spslater spslater left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The merge looks good. Like I just said (I forgot there was a comment box here), I'll make a new pull request for any cosmetic things that don't line up. The newer added {Get,Set}LastModifiedAt functions will still work with events, but won't with anything else.

@arran4 arran4 merged commit 804f4d3 into master Jan 8, 2024
25 checks passed
@arran4 arran4 deleted the pull-66-add-todo-journal branch January 8, 2024 05:48
@arran4
Copy link
Owner Author

arran4 commented Jan 8, 2024

@spslater Will review when they come through. I will wait until all your PRs are though before tagging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants